From: Sandra Loosemore Date: Thu, 8 Nov 2018 03:37:32 +0000 (-0500) Subject: re PR middle-end/42726 (-fno-common documentation inaccuracy) X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=bd21ffae02ebf96a8c120278d7e9f7ce46f4483f;p=gcc.git re PR middle-end/42726 (-fno-common documentation inaccuracy) 2018-11-07 Sandra Loosemore PR middle-end/42726 gcc/ * doc/invoke.texi (Code Gen Options): Clarify -fno-common behavior. From-SVN: r265906 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index a85868c06cd..decc5a0f228 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 e455b91bc75..849bb76dc25 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.