15:57 If they're really that concerned about size, they wouldn't be stuffing the .class files with so much useless data. The bytecode is usually less than 1% of the .class file, while the constant pool takes roughly 90% of it, with a LOT of repetition and redundancy! :P
Hi, how did it store the string hello in the 32bit wide stack, also when you said array objects need to be on the stack. does that mean that all the contiguous memory locations need to be on the stack.?
Second part link: ua-cam.com/video/0Yud4Q2HEz4/v-deo.html
15:57 If they're really that concerned about size, they wouldn't be stuffing the .class files with so much useless data. The bytecode is usually less than 1% of the .class file, while the constant pool takes roughly 90% of it, with a LOT of repetition and redundancy! :P
there is a mistake at 15:33. The instruction mnemonic is icosnt_[m1-5], not iload_[m1-5]
Really wish they showed the actual java bytecode instead of the weird Ruby pet project...
I think it helps clean-up the presentation
professional, thank you Sir
Excellent presentation, thank you
Aggelos Biboudis before commenting you should watch, its a good one.
Starts at 2:50
interesante.
dup2_x2 is to push to the slot 4 instead of 3. the demo is actually dup2_x1, right?
where static string memory will be allocated.
Arun Badhai method area
In method area scp
Hi, how did it store the string hello in the 32bit wide stack, also when you said array objects need to be on the stack. does that mean that all the contiguous memory locations need to be on the stack.?
It just stores a pointer doesn't it, not the whole thing on the stack.
good vedio
布雷 Video, not vedio
ok.
Anyone know a link to the part 2 mentioned?
+Benjamin Cheng
That link is broken, this talk seems to be on the same topic, though it'd been given earlier: vimeo.com/41968163
I think it's this one - ua-cam.com/video/FnDHp3Qya6s/v-deo.html