On 08.08.2014 03:21, Drew DeVault wrote: > On 08/06/2014 01:27 AM, Philipp Klaus Krause wrote: >> On 30.07.2014 04:16, Drew DeVault wrote: I see two options: >> >> 1) sdcc rarely emits jr directly (jr is mostly generated in the >> peephole optimizer), so by using a non-default peephole rule file >> (see pepph-z80.def), one could probably get around the jr issue (or >> you could just change jr back to jp in you processing of the >> assembly source). With the runtime relocation your OS uses and the >> additional nops inserted you don't seem to care much about >> efficiency anyway. >> >> 2) Make sdcc emit your macros instead of jp / call / ld. This would >> be relatively easy for jp and call, since they are only emitted >> from a few places, but harder for ld. You might want to have a look >> at z80/gen.c. > > Changing the peephole rule is probably fine. Will that also work for DJNZ?
sdcc does emit a few jr and djnz directly in code generation (as opposed to from the peepholes, where most of the jr are emitted by changing jp to jr). However, those emitted by code generation are over very short ranges, so if your postprocessing of asm adds a few bytes in between the jump and the target, the target will still be in range. Philipp
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds
_______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
