'if not / unless' optimization change makes my pow test go POW!

["Steve Hay" <SteveHay@planit.com>]

Almost all of the test failures here:

http://www.nntp.perl.org/group/perl.daily-build.reports/2008/09/msg59218
.html

are a result of #34310. I don't understand why, but it's quite
reproduceable: op/pow.t eats memory like it's gone out of fashion and
then goes *POW!* at #34310, but runs OK at #34309.

Likewise for ext/Win32API/File/t/file.t, and probably all the other
failures except ext/Test/Harness/t/prove.t, which I'll get round to
looking at one day...

---

Follow-Ups from:

Nicholas Clark <nick@ccl4.org>
Vincent Pit <perl@profvince.com>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---