Talk:Binary recompiler

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on Binary recompiler. Please take a moment to review my edit. You may add after the link to keep me from modifying it, if I keep adding bad data, but formatting bugs should be reported instead. Alternatively, you can add to keep me off the page altogether, but should be used as a last resort. I made the following changes:
 * Attempted to fix sourcing for http://web.eecs.umich.edu/~jringenb/binary_recomp.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.—cyberbot II  Talk to my owner :Online 14:46, 29 March 2016 (UTC)

DRI introduced a *binary* translator or a *source* translator?
Source-to-source compiler claims that XLT86 translated 8080 assembler language to 8086 assembler language, not 8080 machine code to 8086 machine code. This manual for XLT86 says the same thing.

Did Digital Research also have a binary-to-binary translator, or are the references speaking of a binary-to-binary translator from DRI confused? Guy Harris (talk) 21:04, 5 January 2018 (UTC)
 * XLT86 was an optimizing source-to-source translator, not high-level to high-level, but from assembly code to assembly code. Since there is (almost) a one-to-one correlation between assembly language and actually executable machine code, the sources are somewhat misleading in regard to the nomenclature when they talk about binary recompilation, but not totally confused either.
 * One can think of binary recompilation through XLT86 as a batch process involving a disassembler, the source-to-source translator and an assembler. Disassemblers and assemblers were also available in various forms from Digital Research.
 * Also, XLT86 was not a straight-forward translator carrying out only transliterations, but it performed global data flow analysis and was applying various optimizations. The multi-pass translator translated the input into some binary in-memory structure representing the program graph. This is even closer to binary recompilation, except for that the output was, again, human-readable assembly code rather than a binary image.
 * In summary, the references could have been more clear about it, but nevertheless XLT86 set the groundwork for binary recompilation as well.
 * --Matthiaspaul (talk) 20:19, 22 January 2020 (UTC)