But with jit enabled on x86/freebsd/openbsd, I was having problems with
some of the pow functions. The rt number is #38382. Because of the
compile time optimization, it made it trickier to work with because the
compile time was ok, but the jit runtime wasn't, and it took me a
little while to realize the compile time optimization. I'm not saying
no optimizations should be the default, but an option to disable
compile time optimizations would help with the testing the interpreter
instead of the compiler.
On Feb 8, 2006, at 9:23 AM, Leopold Toetsch wrote:
there's no way to disable optimizations completely, e.g. this pir
.sub main :main
$N0 = pow 2.0, 5.0
.end
Is always converted to this.
main:
set N0, 32
end
This isn't an optimization. The 'pow' opcode is just run at
compiletime.
Which can lead to misleading test results for when pow's actually
broken.
If 'pow' is broken then it's borken. The only case where that would
matter is, when you are compiling a PBC on a machine with a broken
'pow' and ship that PBC.
leo
