Re: [sdcc-devel] aslink

[Michael H. <mic...@ju...>]

Hi Jesus.  Sounds fine by me, but I'll wait until someone who knows the
8051 port better chimes in.

-- Michael

On Mon, 2 Sep 2002, Jesus Calvino-Fraga wrote:

> Does that mean that it is safe to make changes to aslink that are 8051
> specific?  I've been hacking at aslink, so it creates a few default areas
> used to improve data ram and stack usage.  For example, if the upper
> register banks and the bit area are empty, the data variables are put as
> low as possible in internal ram.  Also if  just a few bits are defined,
> data variables are automatically allocated at the next available byte in
> the bit area.  This also allows for stack checking, such as when the stack
> overlaps any other area, or the space for the stack is too small.  If I
> remember correctly, something similar to what the PLM-51 and/or AVC-51
> linkers use to do...
>
> So far, I have made a lot of changes to aslink and a few to sdcc to include
> these improvements.  Do you think these changes are worth including in the
> CVS sdcc?  If yes, what about letting me join the sdcc developers group?
>
> At 12:54 AM 9/3/02 -0400, Michael Hope wrote:
> >On Mon, 2 Sep 2002, Jesus Calvino-Fraga wrote:
> >
> > > Hi all,
> > >
> > > Is the linker 'aslink' used for all target CPUs or just for the 8051/DS390?
> >
> >Half and half.  The z80, gbz80, and mcs51 all use aslink but the gbz80/z80
> >version is different to the mcs51 one as they originally came from
> >different customised bases.  I've looked at merging them before but
> >they've diverged too far.
> >
> >-- Michael
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> sdcc-devel mailing list
> sdc...@li...
> https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>