Ian Lance Taylor writes:
>
> Figuring out what has gone wrong is like optimizing any program. Get
> a profile for your program, e.g., using -pg. Build the program with
> and without -flto, run it, and look at the resulting profiles. A 50%
> slowdown should be fairly obvious. I would guess that
On Mon, Aug 13, 2012 at 8:27 AM, wrote:
> I'm not sure what LTO is supposed to do -- the documentation is not exactly
> clear. But I assumed it should make things faster and/or smaller.
>
> So I tried using it on an application -- a processor emulator, CPU intensive
> code, a lot of 64 bit int
I'm not sure what LTO is supposed to do -- the documentation is not exactly
clear. But I assumed it should make things faster and/or smaller.
So I tried using it on an application -- a processor emulator, CPU intensive
code, a lot of 64 bit integer arithmetic.
Using a compile/assembler run on
