[llvm-commits] Flag to print vectorized loops

[Chris Lattner]

On Nov 26, 2012, at 6:00 PM, Nadav Rotem <nrotem at apple.com> wrote:

> 
> On Nov 26, 2012, at 3:46 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>> 
> 
>> In my opinion, what we really need is an interface that the frontend can use to get information from the backend optimizers. Then the frontend can display this information to users in an appropriate way.
> 
> I  agree. 
> 
>> Furthermore, this information should be structured (we already have a YAML parser, so that might be a good choice),
> 
> YAML is a great way to serialize these messages, and pass them to IDEs, etc.  But I think that we should start discussing the interfaces. 
> 
>> and should probably directly take a Value *, BasicBlock *, Function *, etc. so that the frontend can do the appropriate mapping for the user.
>> 
> 
> +1 

IMO, the right way to build this is something like "InlineAsmDiagnosticHandler" in LLVMContext (but hopefully better, and more structured :).  The basic jist of it is that the backend can push messages up, and the frontend can register its hooks to render them however it likes.  In this case, I agree that clang "Notes" or some new "informational" diagnostic is probably the right way to go.  

-Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20121126/3c616564/attachment.html>