Document push/pop for segment name #pragmas

git-svn-id: svn://svn.cc65.org/cc65/trunk@2908 b7a2c559-68d2-44c3-8de9-860c34a00d81
This commit is contained in:
cuz
2004-03-08 22:35:37 +00:00
parent 40dc3582a9
commit 32307e14e4

View File

@@ -671,6 +671,8 @@ parameter with the <tt/#pragma/.
use another BSS segment, you have to do that yourself, otherwise use another BSS segment, you have to do that yourself, otherwise
uninitialized variables do not have the value zero. uninitialized variables do not have the value zero.
The <tt/#pragma/ understands the push and pop parameters as explained above.
Example: Example:
<tscreen><verb> <tscreen><verb>
#pragma bssseg ("MyBSS") #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 segments. If you use other segments, you have to create a new linker
configuration file. configuration file.
The <tt/#pragma/ understands the push and pop parameters as explained above.
Example: Example:
<tscreen><verb> <tscreen><verb>
#pragma codeseg ("MyCODE") #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 segments. If you use other segments, you have to create a new linker
configuration file. configuration file.
The <tt/#pragma/ understands the push and pop parameters as explained above.
Example: Example:
<tscreen><verb> <tscreen><verb>
#pragma dataseg ("MyDATA") #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 segments. If you use other segments, you have to create a new linker
configuration file. configuration file.
The <tt/#pragma/ understands the push and pop parameters as explained above.
Example: Example:
<tscreen><verb> <tscreen><verb>
#pragma rodataseg ("MyRODATA") #pragma rodataseg ("MyRODATA")