On Fri, Mar 08, 2002 at 04:24:00PM +0000, Nicholas Clark wrote: > On Fri, Mar 08, 2002 at 11:01:07AM -0500, Michael G Schwern wrote: > > On Fri, Mar 08, 2002 at 03:56:49PM +0000, Nicholas Clark wrote: > > > > Hence, is it -DDEBUGGING that's doing the breakage? > > > [Or did I get my assumptions wrong?] > > > > These work: > > > > -g > > -g -DDEBUGGING > > > > These don't: > > > > -O > > -O -DDEBUGGING > > Ah. What does -O0 give you?
Appears to work fine. > It's gcc. Worse. It's egcs. > What does -O -g give you? Same failures as -O. > zero. It should turn the optimiser off, hence avoiding any optimiser > bugs, but not enable debugging. I believe that enabling debugging > causes all automatic variables to be initialised to zero, so leaving > them initialised may smoke out the bug's cause] I really can't analyize an optimizer bug down to more than "its broken". If you sign up for a TestDrive account on the machine now they'll probably have you activated today. Perl's sitting in /tmp/schwern/perl-current. Meanwhile, I'll play the monkey. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One "Please hold while reality is adjusted to match my ideal world." -- njt
