The JIT compiler is oblivious of x86-64 "red zone"

[penberg]

The JIT compiler does not know about x86-64 "red zone":

http://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64/

this means that anything the JIT compiler saves on the stack without explicitly moving the stack pointer can be clobbered by other functions that were compiled with GCC. This might explain odd data corruption for various different applications on x86-64.