[LLVMdev] RFC - Adding an optimization report facility?

[Neil Hickey]

Hi Diego, I really like your suggestion and agree that this could be really
useful to end users looking to understand why the compiler was unable to
apply certain optimisations to the code.

Often, understanding why the compiler failed to auto-vectorise is
incredibly useful information allowing the end user to write the code in a
more amenable form, to allow the compiler to do a better job.

We often use the -ftree-vectorizer-verbose=<n> options in gcc to understand
both which loops were vectorized and which weren't for what reason, it is
much more convenient than reading the generated assembly file :)

I'd like to reiterate Gerolf's comment that different levels of verbosity
would be really useful, personally I'd like to see all the way down to very
detailed analysis of the decisions the compiler is taking if you set the
verbosity level high enough, like -vec-report an -ftree-vectorizer-verbose
in other compilers.

This is something we'd be really interested in seeing added and we had
already started working on something similar ourselves, though it obviously
makes more sense for us to contribute to this effort.

What is the current status of the implementation?

Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140402/3e351b91/attachment.html>