6502/cc65
1
0
Fork 0
mirror of https://github.com/cc65/cc65.git synced 2025-01-10 19:29:45 +00:00
Code Issues Projects Releases Wiki Activity

Updated doc to better reflect current code.

Browse Source 
git-svn-id: svn://svn.cc65.org/cc65/trunk@4283 b7a2c559-68d2-44c3-8de9-860c34a00d81
This commit is contained in:
ol.sc 2009-09-30 21:54:20 +00:00
parent 9ba5252a01
commit ce778c4bb8
1 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/ld65.sgml
View File

@ -950,15 +950,22 @@ __STACKSIZE__=xxx/ on the command line.
<sect1>Builtin configurations<p> <sect1>Builtin configurations<p>
The builtin configurations are part of the linker source. They are also The builtin configurations are part of the linker source. They can be retrieved
distributed together with the machine specific binary packages (usually in the with <tt/--dump-config/ and don't have a special format. So if you need a
doc directory) and don't have a special format. So if you need a special special configuration, it's a good idea to start with the builtin configuration
configuration, it's a good idea to start with the builtin configuration for for your system. In a first step, just replace <tt/-t target/ by <tt/-C
your system. In a first step, just replace <tt/-t target/ by <tt/-C
configfile/. Then go on and modify the config file to suit your needs. configfile/. Then go on and modify the config file to suit your needs.
<sect1>Secondary configurations<p>
Several machine specific binary packages are distributed together with secondary
configurations (in the cfg directory). These configurations can be used with
<tt/-C configfile/ too.
<sect>Special segments<p> <sect>Special segments<p>
The builtin config files do contain segments that have a special meaning for 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 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. loaded at the lowest possible program address on several platforms.
<sect1>HEAP<p> <sect1>ZPSAVE<p>
This segment defines the location of the memory heap used by the malloc The ZPSAVE segment contains the original values of the zeropage locations used
routine. by the ZEROPAGE segment. It is placed in its own segment because it must not be
initialized.