[LLVMdev] RFC - Adding an optimization report facility?

Diego Novillo dnovillo at google.com
Fri Mar 7 06:07:19 PST 2014


On Thu, Mar 6, 2014 at 7:08 PM, Hal Finkel <hfinkel at anl.gov> wrote:

My suggestion is that we start attaching loop-id metadata to loops in the
> frontend, and then also start attaching 'srcloc' metadata, just like we do
> for inline asm statements. This way we can pass back the information we
> need to the frontend for it to identify the loop without too much trouble.
> There may be a better long-term design, but this seems, at least, like an
> easy thing to do in the short term.
>

Why not just using the line table in -gline-tables-only? These reports will
need to latch on arbitrary instructions, not just loop headers. As more
transformations use the infrastructure, they will want to emit the report
on whatever instruction they triggered on.

Diego.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140307/20c4ee55/attachment.html>


More information about the llvm-dev mailing list