4 ms·
> ... it works the same way and largely generates the same machine code How can they make this determination? Do they just eyeball a few sections of the machi
by dj_gitmo 4y ago
> ... it works the same way and largely generates the same machine code
How can they make this determination? Do they just eyeball a few sections of the machine code from each output? Is there some tool that can compare binaries?
Is this just a very literal, function by function, translation from C to Rust?
I don't know much reading/comparing machine code.
- pjmlp 4y agoThey mean the output of JIT compiler, not the binary itself.
- pizza234 4y agoI'm not familiar with what YJIT generates, however, in general terms, if the ASM code for a given bytecode is small enough (Which I think it is), one can just compare them side by side, or just log them and compare them separately. I think a JIT for Ruby should compile relatively small chunks of ASM, not big walls of code (but again, this is my guess).