Whole program optimization and functions-only-called-once.

[Richard Guenther]

On Sun, Nov 15, 2009 at 8:07 AM, Toon Moene <toon@moene.org> wrote:
> Steven Bosscher wrote:
>
>> On Sat, Nov 14, 2009 at 11:12 PM, Richard Guenther
>> <richard.guenther@gmail.com> wrote:
>
>>> I don't even remember which other passes have this kind of cut-offs ..
>>
>> At least CPROP, LCM-PRE, and HOIST (i.e. all passes in gcse.c), and
>> variable tracking.
>
> Are they covered by a --param ?  At least that way I could teach them to go
> on indefinitely ...

I think most of them are.  Maybe we should diagnose the cases where
we hit these limits.

Richard.

> [ The practice with binaries (i.e., the results of builds up until
>  binaries are produced) in my world is: compile once (no matter how
>  much time it takes) and run about 18 hours of a 24 hour period each,
>  until the next compilation - about a year later.
>
>  So it doesn't really matter how much time a compile/link step takes. ]
>
> --
> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
> Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
> At home: http://moene.org/~toon/
> Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html
>