--- a/docs/manual.docbook.sgml	Mon Aug 29 19:05:18 2011 -0600
+++ b/docs/manual.docbook.sgml	Mon Aug 29 19:15:50 2011 -0600
@@ -1330,15 +1330,31 @@
 However, <parameter>flags</parameter> may only be specified on the first
 instance of the section.
 </para>
-<para>There is a single flag supported in <parameter>flags</parameter>. The
-flag <parameter>bss</parameter> will cause the section to be treated as a BSS
-section and, thus, no code will be included in the object file nor will any
-bytes be permitted to be output.</para>
+
+<para><parameter>flags</parameter> is a comma separated list of flags. If a
+flag is "bss", the section will be treated as a BSS section and no
+statements that generate output are permitted.</para>
+
+<para>If the flag is "constant",
+the same restrictions apply as for BSS sections.  Additionally, all symbols
+defined in a constant section define absolute values and will not be
+adjusted by the linker at link time.  Constant sections cannot define
+complex expressions for symbols; the value must be fully defined at assembly
+time.  Additionally, multiple instances of a constant section do not
+coalesce into a single addressing unit; each instance starts again at offset
+0.</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 the section name is "_constants" or "_constant", in any
+combination of upper and lower case, the section is assumed to be a constant
+section.  This assumption can be overridden with the "!constant"
+flag.</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