[llvm-commits] [llvm] r98709 - /llvm/trunk/docs/ReleaseNotes.html

[Andreas Neustifter]

Hi!

On 03/17/2010 05:41 AM, Chris Lattner wrote:
> Author: lattner
> Date: Tue Mar 16 23:41:49 2010
> New Revision: 98709
>
> URL: http://llvm.org/viewvc/llvm-project?rev=98709&view=rev
> Log:
> add a bunch of random and unformatted notes as I am reading
> through tons of old commits.
>
> Modified:
>      llvm/trunk/docs/ReleaseNotes.html
>
> Modified: llvm/trunk/docs/ReleaseNotes.html
> URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ReleaseNotes.html?rev=98709&r1=98708&r2=98709&view=diff
> ==============================================================================
> --- llvm/trunk/docs/ReleaseNotes.html (original)
> +++ llvm/trunk/docs/ReleaseNotes.html Tue Mar 16 23:41:49 2010
> @@ -441,6 +444,33 @@
[...]
> +MC encoding and disassembler apis.
> +Optimal Edge Profiling?
> +Instcombine is now a library, has its own IRBuilder to simplify itself.
[...]

The Optimal Edge Profiling implementation in 2.6 was more a proof of 
concept. The current implementation (the one that will go into 2.7) is 
now stable and (as far as my tests go) bug free.

The profiling with instrumentation via "opt" and analysis via the tool 
"llvm-prof" should Work As Expected (TM).

Two things are missing:

*) Still missing is the modification of all -std-compile-opt passes to 
update the profiling information according to the changes made to the 
CFG, I'm planning to do this after my master thesis is finished. This 
will enable all passes to use the ProfileInfo if available and base 
decisions on that information.

*) GCC has the options "-pg", "-fprofile-arcs" and "--coverage" that 
insert profiling code and "-fprofile-use" to use them the next time 
during compilation. I guess this options should also work properly in 
llvm-gcc and clang?

Cheers, Andi