cool!
i once tried to write a brainfuck jit compiler (that just appends raw bytes to a buffer and runs it as x86 machine code if it hits a branching instruction like [ / ])
That’s cool. Mine is just an interpreter for execution but it has breakpoints, watchpoints, and save states. I’ve thought about trying to do some form of JIT or at least AOT but I haven’t yet made an attempt. Besides for a debugger that’s counter productive.
save states are something i’ve seen very few debugger-enabled interpreters have.
on paper, it would probably be as easy as storing the state of the interpreter in a format like a core dump (only requires the ability of reflection)
cool! i once tried to write a brainfuck jit compiler (that just appends raw bytes to a buffer and runs it as x86 machine code if it hits a branching instruction like
[/])That’s cool. Mine is just an interpreter for execution but it has breakpoints, watchpoints, and save states. I’ve thought about trying to do some form of JIT or at least AOT but I haven’t yet made an attempt. Besides for a debugger that’s counter productive.
save states are something i’ve seen very few debugger-enabled interpreters have. on paper, it would probably be as easy as storing the state of the interpreter in a format like a core dump (only requires the ability of reflection)