22 Sep
2002
22 Sep
'02
6:05 p.m.
Ah. Replacing the implementation of F_ESCAPE_CATCH fixed the problem. *committing*
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2002-09-22 23:15: Subject: catch { catch { break foo; }; };
The following invocation
pike -e 'foo: for(;;) { catch { catch { break foo; }; }; }'
makes Pike bomb out on POWER with machine code optimizations. The stack is a little too messed up for me to figure out where it went wrong just from the post mortem though. What sequence of bytecodes will be generated by this code?
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)