Re: Optimization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



so what flag can I give gcc to tell it to inline everything, or as much as possible??? Our code already takes 16 hours to build on sparc, using -O2 -g -finline-limit=2750.

I've profiled the code but I'm not exactly sure what to do with it now that I've got it. Someone sail something about gproff but I don't know exactly what I'm looking for.

-brian

Brian D. McGrew { brian@xxxxxxxxxxxxxxxxxxx || pacemakertaker@xxxxxxxxx }
--
> YOU! Off my planet!
On Apr 27, 2004, at 8:02 AM, Ian Lance Taylor wrote:


Brian D.McGrew <brian@xxxxxxxxxxxxx> writes:

As for the -O0 flag, I posted the wrong trace file.  In the release
trees, we use -O2 -g -finline-limit=2750 on all versions, all
platforms.  My bad.

I doubt this is your problem, but -finline-limit will have a different effect on i386 and SPARC, since the SPARC will normally require more instructions. Although -finline-limit is expressed in terms of pseudo-instructions, gcc pseudo-instructions are different on i386 and SPARC. It would normally be appropriate to use a larger -finline-limit on SPARC.

As I say, I doubt this is your problem.  I have no idea what your
problem is.  It's fairly unlikely that anybody can tell you what is
wrong here.

As was already suggested, try using a profiler to see where the hot
spots are in your slow version.  Perhaps gcc is egregiously
miscompiling something on SPARC.

Ian



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux