On Wed, 4 Jan 2006, Joshua Hoblitt via RT wrote:
> Andy,
>
> Were you caught by either "takes too long" or "Overwhelms some
> compilers."?
Well, it hadn't quite overwhelmed the compiler yet -- it was swapping like
mad for at least 20 minutes and still growing, and several other processes
(including spamassassin, alas) had died due to out-of-memory-errors, but
the compiler hadn't quite given up yet. I suspect it would have, had I
let it continue.
> I'm wondering if it's worth disabling optimizations for
> those compilation units if nobody noticed a problem in the period
> between the tree reorganization and the breakage of --optimize.
It's very hard to portably test for this sort of thing. Even in perl5's
Configure, I eventually gave up on it, and just made sure it was well
documented in the INSTALL file what to do. (The usual culprit there is
toke.c.)
As to how widespread a problem this could be, I really don't know. It's
possible nobody noticed a problem because nobody tested it on anything
other than gcc.
--
Andy Dougherty [EMAIL PROTECTED]
