This is the mail archive of the
mailing list for the GCC project.
Re: GCC inline parameters (PR 10160 testcase)
- From: Andreas Jaeger <aj at suse dot de>
- To: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Cc: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com
- Date: Fri, 02 May 2003 20:30:15 +0200
- Subject: Re: GCC inline parameters (PR 10160 testcase)
- References: <200305021825.h42IPmxv027818@hiauly1.hia.nrc.ca>
"John David Anglin" <firstname.lastname@example.org> writes:
> I believe that we are about to ship 3.3 with a set of inline parameter
> defaults that are way too agressive. These can cause huge increases
> in compilation time and memory over that with a more conservative
> set of parameters.
> This has been discussed before and Mark made some improvements.
> However, PR 10160 hasn't been resolved and the problem with the
> default inline parameter set remains.
> For example, I see the following building xforms/Dialogs.C from
> lyx-1.3.1 on hppa2.0-hp-hpux11.11:
> Current Inline Parameters Patched Parameters
> Compilation Time ~ 5 hours ~ 2 minutes
> Max Resident Size ~ 650 MB ~ 60 MB
> Stripped lyx Executable ~ 10 MB ~ 7 MB
> On the PA, branches within functions become much less efficient when
> the code size exceeds ~ 240KB.
> The enclosed patch for 3.3 has been tested on hppa2.0-hp-hpux11.11 with
> no regressions.
What kind of performance difference does this give us? I fear that
this change will speed up compilation but slow down execution and
would therefore like to see some performance data of compiled code
SuSE Labs email@example.com