Mercurial > hg-old > index.cgi
changeset 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 | f0527dc3804d |
children | b061350c17e4 |
files | doc/manual.docbook.sgml |
diffstat | 1 files changed, 18 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/manual.docbook.sgml Sat Jan 31 05:30:06 2009 +0000 +++ b/doc/manual.docbook.sgml Sat Jan 31 06:32:27 2009 +0000 @@ -899,6 +899,11 @@ section and, thus, no code will be included in the object file nor will any bytes be permitted to be output.</para> <para> +If the section name is "bss" or ".bss" in any combination of upper and +lower case, the section is assumed to be a BSS section. In that case, +the flag <parameter>!bss</parameter> can be used to override this assumption. +</para> +<para> If assembly is already happening within a section, the section is implicitly ended and the new section started. This is not considered an error although it is recommended that all sections be explicitly closed. @@ -1016,6 +1021,19 @@ </varlistentry> <varlistentry> +<term>cescapes</term> +<listitem> +<para> +This pragma will cause strings in the FCC, FCS, and FCN pseudo operations to +have C-style escape sequences interpreted. The one departure from the official +spec is that unrecognized escape sequences will return either the character +immediately following the backslash or some undefined value. Do not rely +on the behaviour of undefined escape sequences. +</para> +</listitem> +</varlistentry> + +<varlistentry> <term>undefextern</term> <listitem> <para>