Re: abysmal code generated by gcc 3.2

[Dale Johannesen <dalej@apple.com>]

On Monday, October 21, 2002, at 12:21  PM, Mike Stump wrote:
> On Monday, October 21, 2002, at 11:45 AM, Denys Duchier wrote:
>> Mike Stump <mrs@apple.com> writes:
>>> and experimenting
>>> with all the relevant compiler flags, for example, see the following
>>> parameters: max-inline-insns-single, max-inline-insns,
>>> max-inline-slope, and min-inline-insns.
>>
>> uh? except for max-inline-insns, I never heard of the others.  Are
>> these new (and what do they mean? - is that maybe documented in CVS).
>
> I'll assume all of these are documented in the manual,

No, they are not.  Perhaps the patch that added them

2002-04-27  Kurt Garloff <garloff@suse.de>

         * tree-inline.c (inlinable_function_p): Improve heuristics
         by using a smoother function to cut down allowable inlinable 
size.
         * param.def: Add parameters max-inline-insns-single,
         max-inline-slope, min-inline-insns that determine the exact
         shape of the above function.
         * param.h: Likewise.

should be reverted until this is fixed.  (-fmax-inline-insns was broken 
at
the same time so that it no longer works to increase the size limit.)