3 ms·
I’m just gonna jump in. The JVM has no problem hot loading, unloading, or redefining presently executed code. What I’m trying to say is JIT’ing dynamically loa
by valarauca1 9y ago
I’m just gonna jump in.
The JVM has no problem hot loading, unloading, or redefining presently executed code. What I’m trying to say is JIT’ing dynamically loaded code isn’t rocket science
- gravypod 9y agoIt's much more complicated and a much lower on the cost-benefit totem-pole than... 1. Inlining 2. Compiling bytecode for a specific set of input and output types 3. Object Recycling 4. Runtime-compiling to machine code Things like that. edit: I may be wrong. I'd love to see an example of a VM that implements what you're thinking.
- dr_zoidberg 9y agoWhile the name of the talk implies it's a generally-speaking-talk, Click goes into a lot of detail of how the JVM works in his "A Crash Course in Modern Hardware" presentation[0]. I saw it a while ago, but I think he does mention those things. Of course that's the one I saw and remember, but you could probably find another presentation in which he goes into much better detail about the JVM and its inner workings. [0] https://www.youtube.com/watch?v=OFgxAFdxYAQ https://www.youtube.com/watch?v=OFgxAFdxYAQ