From: Mark Mason <mmason@up...> - 2009-06-23 18:19:33
I've started a port of SDCC to the 80196. I'm taking an incremental
approach - porting all parts of the SDCC toolchain, but only a couple
of instructions at a time (add some new instructions to the compiler,
and then adding the necessary as, link and simulator bits to support
that). For the most part I'm finding it fairly straightforward, but
with a few exceptions.
Specifically, the linker header file aslink.h seems to have some very
8051 specific information buried in it wrt relocation values. Is it
the intention that other targets leverage these values (and add
architecture specific extensions only when absolutely necessary), or
is this simply a holdover from being ported to the 8051 first, and I
should simply ignore these values and define my own for the 80196?
Any guidance would be appreciated. Either way should be simple enough
to implement, but I want to do it the "right" way so that patches will
eventually be accepted back.
Thanks in advance!