This is the mail archive of the
mailing list for the GCC project.
Re: GCC 3.0.3 produces large code
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- To: Joe Buck <jbuck at synopsys dot com>
- Cc: hb at x256 dot org (Nicholas Adrian Vinen), zack at codesourcery dot com (Zack Weinberg), i dot krabbe at dokom dot net (Ingo Krabbe), gcc at gcc dot gnu dot org
- Date: 01 Feb 2002 18:36:20 +0100
- Subject: Re: GCC 3.0.3 produces large code
- Organization: CodeSourcery, LLC
- References: <200202011714.JAA17263@atrus.synopsys.com>
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
When the small functions are static one used in large fonctions, that
is no option.
CodeSourcery, LLC http://www.codesourcery.com