Re: [Sdcc-user] Data area immediately following code

2020-04-02 Thread Alan Cox
On Fri, 3 Apr 2020 11:06:32 +1100 Brad Robinson wrote: > Thanks guys. > > I really don't want to have to install an additional toolchain if I > can avoid it. > > I just discovered the following messages which provide some seemingly > relevant clues but doesn't really address collapsing INITIALI

Re: [Sdcc-user] Data area immediately following code

2020-04-02 Thread Brad Robinson
Thanks guys. I really don't want to have to install an additional toolchain if I can avoid it. I just discovered the following messages which provide some seemingly relevant clues but doesn't really address collapsing INITIALIZER and INITIALIZED areas into one: https://sourceforge.net/p/sdcc/mai

Re: [Sdcc-user] Data area immediately following code

2020-04-02 Thread Sergey Belyashov
Hi, SDCC uses very simple scheme for storing initialization data. It generates two copies of variables, one copy is initialization data which is stored after code section, and copied to variables area on startup. I think, it is caused by very simple linkers supported. More complex linkers can do th

Re: [Sdcc-user] Data area immediately following code

2020-04-02 Thread Alan Cox
On Wed, 1 Apr 2020 18:01:37 +1100 Brad Robinson wrote: > Hey All, > > I've got a Z80 project where the generated image will be loaded > directly into RAM and therefore the initialization data doesn't need > to be copied from the image to a specified RAM area. > > How can I configure SDCC to gen