From ce778c4bb8315f03f4aa25c6823b1db90f1e67b0 Mon Sep 17 00:00:00 2001 From: "ol.sc" Date: Wed, 30 Sep 2009 21:54:20 +0000 Subject: [PATCH] Updated doc to better reflect current code. git-svn-id: svn://svn.cc65.org/cc65/trunk@4283 b7a2c559-68d2-44c3-8de9-860c34a00d81 --- doc/ld65.sgml | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/doc/ld65.sgml b/doc/ld65.sgml index 5e9a777ef..4afaef5c7 100644 --- a/doc/ld65.sgml +++ b/doc/ld65.sgml @@ -950,15 +950,22 @@ __STACKSIZE__=xxx/ on the command line. Builtin configurations

-The builtin configurations are part of the linker source. They are also -distributed together with the machine specific binary packages (usually in the -doc directory) and don't have a special format. So if you need a special -configuration, it's a good idea to start with the builtin configuration for -your system. In a first step, just replace Secondary configurations

+ +Several machine specific binary packages are distributed together with secondary +configurations (in the cfg directory). These configurations can be used with +Special segments

The builtin config files do contain segments that have a special meaning for @@ -983,10 +990,11 @@ This segment contains the startup code which initializes the C software stack and the libraries. It is placed in its own segment because it needs to be loaded at the lowest possible program address on several platforms. -HEAP

+ZPSAVE

-This segment defines the location of the memory heap used by the malloc -routine. +The ZPSAVE segment contains the original values of the zeropage locations used +by the ZEROPAGE segment. It is placed in its own segment because it must not be +initialized.