Seongbae Park ??? ??? wrote:
This is the intended behavior, though now I see that the documentation
isn't very clear.
Can you fix the documentation? As it stands now, it is easy for a user
to be misguided into thinking -fprofile-arcs and fbranch-probabilities
combination would work.
Just out
Seongbae Park ??? ??? wrote:
On Thu, Jan 8, 2009 at 10:11 AM, Hariharan wrote:
Hi Seongbae,
Does that mean that someone cant use the profile just to annotate branches
(and get better code by that), without having to get the additional baggage
of "unroll-loops", "peel-loops" etc?
You can do
On Thu, Jan 8, 2009 at 10:11 AM, Hariharan wrote:
> Hi Seongbae,
> Does that mean that someone cant use the profile just to annotate branches
> (and get better code by that), without having to get the additional baggage
> of "unroll-loops", "peel-loops" etc?
You can do that by selectively turning
Hi Seongbae,
Does that mean that someone cant use the profile just to annotate
branches (and get better code by that), without having to get the
additional baggage of "unroll-loops", "peel-loops" etc?
In my case, i am interested in not bloating the code size, but get any
performance that is t
This is the intended behavior, though now I see that the documentation
isn't very clear.
You need to use -fprofile-use - the typical usage scenario is to
compile with -fprofile-generate
to build an executable to do profile collection, and then compile with
-fprofile-use
to build optimized code usin
