Re:Libriscv: RISC-V Binary Translation
by rcgorton on Thursday December 31, 2020 @11:40AM
(#25594210)
Out of curiosity, what is the use case?
RISC-V is new enough that it is unlikely to be needed for 'dusty-deck' (source code long lost) that was needed for the VAX --> Alpha binary translators, or for Univac (ones complement!) to X86_64.
Why require a JIT? For static binary translators (based upon experience) the biggest difficulty is a combination of variable-length instruction decode and/or self-modifying code (requires an interpreter) and/or re-entrant-into-the-middle-of-an-instruction (easiest to handle with an interpreter).
[ Parent
| on HN ]
Actually I think the biggest problem is predicting correctly all the jump targets.
Re:Libriscv: RISC-V Binary Translation
by non-e-moose on Friday January 01, 2021 @04:57PM
(#25607624)
Kenoph: is your company looking for people with experience in binary translation/compilers? My URL: http://gorton-machine.org/rick/index.html and resume hangs off of that.
Regards,
Richard
For an overview of static translators: https://www.hpl.hp.com/hpjournal/dtj/vol4num4/toc.htm, article 9 ('Binary Translation')