[doc,committed] clarify -fno-common behavior

Message ID d1909df8-8ba6-c558-ccd1-f6ee45ec3e19@codesourcery.com
State New
Headers show
Series
  • [doc,committed] clarify -fno-common behavior
Related show

Commit Message

Sandra Loosemore Nov. 8, 2018, 3:39 a.m.
I've checked in this patch to fix a minor but long-standing bug in the 
description of -fno-common, PR 42726.

-Sandra

Patch

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.