|
how do we feel about jitters? are they true compilers or a dangerous heresy?
|
#
¿
Jun 27, 2017 21:21
|
|
|
|
| # ¿ May 1, 2024 21:48 |
|
|
rjmccall posted:having a jit enables some really neat dynamic code generation and specialization tricks. i'd love to see more language implementations based on a sane language + execution environment that really take intelligent advantage of both static and dynamic information how good is modern jitted code compared to what's emitted by a traditional toolchain these days anyway? i've heard about the ability to use info you don't have at compile time to potentially produce better code before, but i have no idea how much of a difference it makes in practice. or any idea what traditional optimizations aren't possible when you're jitting, if any
|
|
#
¿
Jun 28, 2017 16:23
|
|
|
thanks for this, i like compilers but i've never had much experience with them beyond using them the part about optimizing for a specific platform did remind me of the hell of debugging optimized code on some game consoles though. under most circumstances you can just use a debug build, but when you're mostly doing network stuff, everything's asynchronous and bugs depend on timing, so whatever you want to reproduce tends to just disappear on a debug build. symbols don't mean much for optimized code, so you're stuck looking at the disassembled executable. and holy poo poo do console compilers/linkers love to emit the most hosed up spaghetti hell garbage. i mean, i get why they do that, but it makes you long for the simple optimized x64 assembly you get on pc
|
|
#
¿
Jun 28, 2017 21:49
|
|