[sdcc-devel]Pic Port

[Michel V. d. B. <mic...@lu...>]

> Message: 4
> Date: Tue, 13 Feb 2001 08:27:45 +0100 (MET)
> From: Daniel Drotos <dr...@ma...>
> To: <sdc...@li...>
> Subject: Re: [sdcc-devel]CALL Graph (was pic Port)
> Reply-To: sdc...@li...
> 
> On Mon, 12 Feb 2001, Sandeep Dutta wrote:
> 
> > The cleanest way to do the overlay stuff is with the linker. The compiler
> 
> What about defining common object format for object files generated by
> assemblers and using just one linker for every targets (51, avr, pic,
> ...) Just an idea...
> 
> Daniel
> 
I have the impression that the current linker is almost independent of
the target.
There are of course some idiosyncrasies. For example in the Pic an
address in an assembled instruction is not exactly aligned on a byte
boundary (everything has to be packed in 14 bits) but this would require
only a slight extension of the .rel format  it seems.

I am new to this list (and to sdcc), but what is the reason that every
target in sdcc seems to have a different linker (or am I wrong here?,
the source tree is rather confusing)? Wouldn't it be better to have one
linker? Then the overlaying code for local variables would have to be
written only once. This looks more attractive.

(Scott: would it be hard for gpasm to produce .rel files?)
Michel