3 ms·
Okay, then how are stack traces and de-opt events handled? These are the _really_ hard problems with JIT compilers. Tracking the IP location in a block of ASM
by valarauca1 9y ago
Okay, then how are stack traces and de-opt events handled?
These are the _really_ hard problems with JIT compilers. Tracking the IP location in a block of ASM may result in a 3+ Java “methods” being executed at once.
- chrisseaton 9y agoWhen you install code you need to provide a frame map and metadata that maps registers, stack locations and IPs to locals, objects and bytecode. Consider following the advice I put in the document. Open it up in Eclipse and explore using standard Java tools and discover for yourself. That was the whole point.
- chrisseaton 9y agoNow I'm at a desk, I can say start looking at the FrameState class. https://github.com/graalvm/graal/blob/cd655e1df4f388c78364f00017f0299833f03669/compiler/src/org.graalvm.compiler.nodes/src/org/graalvm/compiler/nodes/FrameState.java https://github.com/graalvm/graal/blob/cd655e1df4f388c78364f0... And that's the beauty of it! If you were interested in frame states, typing FrameState into Eclipse will have found this, and then start looking at what calls these methods.