On 2/9/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > 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.
Is there a reason why this can't be "turned off" like this: convert $N0 = pow 2.0, 5.0 to $N9999 = 2.0 $N0 = pow N9999, 5.0 where N9999 is an otherwise unused register. If the only problem is that pow can't be called with 2 constants, this would trivially solve it. ps. The syntax might be wrong, as I don't program in parrot. I'm just following the conversation. -- Markus Laire
