From 08ace7f7741fdd7772224136fdcc52fb5018e766 Mon Sep 17 00:00:00 2001 From: sandra Date: Thu, 8 Nov 2018 03:37:32 +0000 Subject: [PATCH] 2018-11-07 Sandra Loosemore PR middle-end/42726 gcc/ * doc/invoke.texi (Code Gen Options): Clarify -fno-common behavior. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@265906 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 5 +++++ gcc/doc/invoke.texi | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index a85868c06cd9..decc5a0f228f 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2018-11-07 Sandra Loosemore + + PR middle-end/42726 + * doc/invoke.texi (Code Gen Options): Clarify -fno-common behavior. + 2018-11-07 Sandra Loosemore * doc/invoke.texi: Remove leading dash from @opindex entries diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index e455b91bc75f..849bb76dc25d 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -13294,7 +13294,7 @@ C, and on some targets may carry a speed or code size penalty on 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. -- 2.47.3