This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC 3.0.3 produces large code


Joe Buck <jbuck@synopsys.COM> writes:

| >    I agree, like I said, small functions should be optimised for space
| > really, large functions with big loops for speed. Actually, most of my
| > inner loops are in assembly language, so for the C++ code I actually
| > prefer size optimisation so that as much will stay in cache as possible.
| 
| I don't see any reason why this should be true in general.  What should
| happen in my view is that a user who has strong ideas like this would
| be free to sort his/her functions into separate compilation units, using
| -Os to optimize some for space and -O2 or -O3 to optimize others for
| speed.

When the small functions are static one used in large fonctions, that
is no option. 

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]