Added explanation for --codesize

git-svn-id: svn://svn.cc65.org/cc65/trunk@753 b7a2c559-68d2-44c3-8de9-860c34a00d81

doc/cc65.sgml

@@ -78,6 +78,7 @@ Long options:
   --bss-name seg        Set the name of the BSS segment
   --check-stack         Generate stack overflow checks
   --code-name seg       Set the name of the CODE segment
+  --codesize x          Accept larger code by factor x
   --cpu type            Set cpu type
   --data-name seg       Set the name of the DATA segment
   --debug               Debug mode
@@ -125,6 +126,14 @@ Here is a description of all the command line options:
   Set the name of the code segment.
 
 
+  <tag><tt>--codesize x</tt></tag>
+
+  This options allows finer control about speed vs. size decisions in the
+  code generation phase. 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 200/).
+
+
   <tag><tt>--cpu CPU</tt></tag>
 		      
   A new, still experimental option. You may specify "6502" or "65C02" as
@@ -254,7 +263,8 @@ Here is a description of all the command line options:
   Using <tt/-Oi/, the code generator will inline some code where otherwise a
   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.
+  make the code visible for the optimizer. <tt/-Oi/ is an alias for
+  <tt/--codesize 200/.
 
   <tt/-Or/ will make the compiler honor the <tt/register/ keyword. Local
   variables may be placed in registers (which are actually zero page