On Feb 8, 2006, at 22:28, Joshua Isom wrote:
but an option to disable compile time optimizations would help with the testing the interpreter instead of the compiler
It's not an optimization and it can't be turned off, as there are no such opcodes like 'pow_i_ic_ic'. And again - the evaluation of that constant is using the parrot *runtime* (compilation is runtime, just earlier ;) . And if a JITted program behaves differently that's still another case.
See also compilers/imcc/optimizer.c:eval_ins and especially line 655. leo
