On Fri, 3 Apr 2020 11:06:32 +1100 Brad Robinson <brobin...@toptensoftware.com> 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 INITIALIZER and > INITIALIZED areas into one: > > https://sourceforge.net/p/sdcc/mailman/message/34781898/ > > I guess I need to dig into understanding the linker scripts and see if > I can figure it out. The SDCC linker cannot as far as I can tell do this. Even if you tell it to put them both in the same place you don't know which one will end up there. See https://github.com/EtchedPixels/FUZIX/blob/master/Library/tools/binman.c which is how I work around this ugly limit for Fuzix. The Fuzix one also patches a header block with things that the SDCC linker is not able to resolve itself (which to be fair is a limit it shares with a lot of linkers except cc65 and lwtools for 6809). but you can just ignore that bit. There are also tools in that github for generating relocatable binaries. Another thing to check is whether Z88DK has addressed this. It uses a modified SDCC as the main compiler and if so you could just switch to Z88DK instead. > > SDCC uses very simple scheme for storing initialization data. There are also seperate initializers in code generated for some stuff which waste tons of space. Alan _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
