1
0
mirror of https://github.com/cc65/cc65.git synced 2024-12-23 04:30:10 +00:00

Fixed a few inaccuracies the the description of the --codesize option.

git-svn-id: svn://svn.cc65.org/cc65/trunk@4160 b7a2c559-68d2-44c3-8de9-860c34a00d81
This commit is contained in:
uz 2009-09-12 22:04:35 +00:00
parent c271f18d00
commit 4ee6bf6f2c

View File

@ -131,7 +131,7 @@ Here is a description of all the command line options:
This options allows finer control about speed vs. size decisions in the code
generation and optimization phases. It gives the allowed size increase
factor (in percent). The default is 100 when not using <tt/-Oi/ and 200 when
using <tt/-Oi/ (<tt/-Oi/ is the same as <tt/--codesize&nbsp;200/).
using <tt/-Oi/ (<tt/-Oi/ is the same as <tt/-O --codesize&nbsp;200/).
<tag><tt>--cpu CPU</tt></tag>
@ -340,7 +340,7 @@ Here is a description of all the command line options:
runtime functions would have been called, even if the generated code is
larger. This will not only remove the overhead for a function call, but will
make the code visible for the optimizer. <tt/-Oi/ is an alias for
<tt/--codesize&nbsp;200/.
<tt/-O --codesize&nbsp;200/.
<tt/-Or/ will make the compiler honor the <tt/register/ keyword. Local
variables may be placed in registers (which are actually zero page
@ -429,7 +429,7 @@ and the one defined by the ISO standard:
those functions with pointers to user-written, not-fastcall functions.
<p>
<item> The <tt/volatile/ keyword doesn't have an effect. This is not as bad
as it sounds, since the 6502 has so few registers that it isn't
as it sounds, since the 6502 has so few registers that it isn't
possible to keep values in registers anyway.
<p>
</itemize>