Document push/pop for segment name #pragmas

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

diff --git a/doc/cc65.sgml b/doc/cc65.sgml
index e939de852b42739c6d8e34e6090bf8c1aa6d0679..d9030c078705245def5db2d7e5f409f0ea5a4089 100644 (file)
--- a/doc/cc65.sgml
+++ b/doc/cc65.sgml
@@ -196,7 +196,7 @@ Here is a description of all the command line options:
   switch: <tt/-Or/ will enable both, the optmizer and register variables.
 
   For more information about register variables see <ref id="regvars"
-  name="register variables">. 
+  name="register variables">.
 
   The compiler setting can also be changed within the source file by using
   <tt><ref id="pragma-regvars" name="#pragma regvars"></tt>.
@@ -671,6 +671,8 @@ parameter with the <tt/#pragma/.
   use another BSS segment, you have to do that yourself, otherwise
   uninitialized variables do not have the value zero.
 
+  The <tt/#pragma/ understands the push and pop parameters as explained above.
+
   Example:
   <tscreen><verb>
                #pragma bssseg ("MyBSS")
@@ -734,6 +736,8 @@ parameter with the <tt/#pragma/.
   segments. If you use other segments, you have to create a new linker
   configuration file.
 
+  The <tt/#pragma/ understands the push and pop parameters as explained above.
+
   Example:
   <tscreen><verb>
        #pragma codeseg ("MyCODE")
@@ -750,6 +754,8 @@ parameter with the <tt/#pragma/.
   segments. If you use other segments, you have to create a new linker
   configuration file.
 
+  The <tt/#pragma/ understands the push and pop parameters as explained above.
+
   Example:
   <tscreen><verb>
        #pragma dataseg ("MyDATA")
@@ -766,6 +772,8 @@ parameter with the <tt/#pragma/.
   segments. If you use other segments, you have to create a new linker
   configuration file.
 
+  The <tt/#pragma/ understands the push and pop parameters as explained above.
+
   Example:
   <tscreen><verb>
        #pragma rodataseg ("MyRODATA")