On Wed, Oct 1, 2014 at 2:05 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum 10353@lyskom.lysator.liu.se wrote:

No problem, the test program triggered the bug consistently, so it was easy to find and fix the bug.

Fixed in current Pike 8.0.

Thanks for that! Confirmed successful.

It actually took me a while to make that test program. The failing code was deep inside several levels of indirection, but when I tried to do the same thing manually, I invariably used a string literal instead of a string variable - and then it worked perfectly :)

But I'm glad there are these occasional over-optimization bugs. They're part and parcel with a highly optimized interpreter, and that's something I love about Pike.

ChrisA