I've checked in this patch to fix a minor but long-standing bug in the
description of -fno-common, PR 42726.
-Sandra
2018-11-07 Sandra Loosemore <san...@codesourcery.com>
PR middle-end/42726
gcc/
* doc/invoke.texi (Code Gen Options): Clarify -fno-common behavior.
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi (revision 265904)
+++ gcc/doc/invoke.texi (working copy)
@@ -13294,7 +13294,7 @@ C, and on some targets may carry a speed
variable references.
The @option{-fno-common} option specifies that the compiler should instead
-place uninitialized global variables in the data section of the object file.
+place uninitialized global variables in the BSS section of the object file.
This inhibits the merging of tentative definitions by the linker so
you get a multiple-definition error if the same
variable is defined in more than one compilation unit.
