# HG changeset patch # User lost # Date 1233383547 0 # Node ID 71561c12b20b1ca8f2ca13473de698c78014673b # Parent f0527dc3804ddca22351eb48776544cb700d19e2 Updated docs to reflect new cescapes pragma and discuss implicit assumption of the bss section flag for sections named bss and .bss diff -r f0527dc3804d -r 71561c12b20b doc/manual.docbook.sgml --- 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. +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 !bss can be used to override this assumption. + + 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 @@ +cescapes + + +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. + + + + + undefextern