comparison doc/manual.docbook.sgml @ 159:71561c12b20b

Updated docs to reflect new cescapes pragma and discuss implicit assumption of the bss section flag for sections named bss and .bss
author lost
date Sat, 31 Jan 2009 06:32:27 +0000
parents f0881c115010
children 751b99efb1fc
comparison
equal deleted inserted replaced
158:f0527dc3804d 159:71561c12b20b
897 <para>There is a single flag supported in <parameter>flags</parameter>. The 897 <para>There is a single flag supported in <parameter>flags</parameter>. The
898 flag <parameter>bss</parameter> will cause the section to be treated as a BSS 898 flag <parameter>bss</parameter> will cause the section to be treated as a BSS
899 section and, thus, no code will be included in the object file nor will any 899 section and, thus, no code will be included in the object file nor will any
900 bytes be permitted to be output.</para> 900 bytes be permitted to be output.</para>
901 <para> 901 <para>
902 If the section name is "bss" or ".bss" in any combination of upper and
903 lower case, the section is assumed to be a BSS section. In that case,
904 the flag <parameter>!bss</parameter> can be used to override this assumption.
905 </para>
906 <para>
902 If assembly is already happening within a section, the section is implicitly 907 If assembly is already happening within a section, the section is implicitly
903 ended and the new section started. This is not considered an error although 908 ended and the new section started. This is not considered an error although
904 it is recommended that all sections be explicitly closed. 909 it is recommended that all sections be explicitly closed.
905 </para> 910 </para>
906 </listitem> 911 </listitem>
1009 When in force, this pragma enables an optimization affecting indexed addressing 1014 When in force, this pragma enables an optimization affecting indexed addressing
1010 modes. When the offset expression in an indexed mode evaluates to zero but is 1015 modes. When the offset expression in an indexed mode evaluates to zero but is
1011 not explicity written as 0, this will replace the operand with the equivalent 1016 not explicity written as 0, this will replace the operand with the equivalent
1012 no offset mode, thus creating slightly faster code. Because of the advantages 1017 no offset mode, thus creating slightly faster code. Because of the advantages
1013 of this optimization, it is enabled by default. 1018 of this optimization, it is enabled by default.
1019 </para>
1020 </listitem>
1021 </varlistentry>
1022
1023 <varlistentry>
1024 <term>cescapes</term>
1025 <listitem>
1026 <para>
1027 This pragma will cause strings in the FCC, FCS, and FCN pseudo operations to
1028 have C-style escape sequences interpreted. The one departure from the official
1029 spec is that unrecognized escape sequences will return either the character
1030 immediately following the backslash or some undefined value. Do not rely
1031 on the behaviour of undefined escape sequences.
1014 </para> 1032 </para>
1015 </listitem> 1033 </listitem>
1016 </varlistentry> 1034 </varlistentry>
1017 1035
1018 <varlistentry> 1036 <varlistentry>