Hello Dave! > One achitectural problem here is that GCC doesn't emit bytes. It emits > ASCII text, in the form of assembly instructions, and it's > not always easy to predict how they'll look by the time they've been > through the assembler and then had relocs applied by the > linker. (Indeed, to know what particular bytes you'd end up with you'd > need to do everything the assembler and linker does, which > is why we have an assembler and linker - the stuff GCC emits isn't > directly executable...) I know that. So maybe my current way (compile -> find duplicates -> define duplicates -> reuse them in fresh compile) is the easiest way to do that.
> Shouldn't this be done in the linker instead? Well, can the linker change the instruction sequences? Ie. put a JMP instead of other code? Regards, Phil -- Versioning your /etc, /home or even your whole installation? Try fsvs (fsvs.tigris.org)!