Hi, I've noticed that the description of -fcommon that gets printed with "gcc -v --help" is exactly the opposite of what this option actually does.
With -fcommon, different global variables w/o initial value are plced in common blocks, similar to fortran named common blocks, while with -fno-common, those variables are placed in the .bss segment. I believe the description is describing the "flag_no_common", but that is not what the user needs to know. Bootstrapped and reg-tested on x86_64-pc-linux-gnu. Is it OK for trunk? Thanks Bernd.
2019-10-20 Bernd Edlinger <bernd.edlin...@hotmail.de> * common.opt (-fcommon): Fix description. Index: gcc/common.opt =================================================================== --- gcc/common.opt (revision 277155) +++ gcc/common.opt (working copy) @@ -1132,7 +1132,7 @@ fcommon Common Report Var(flag_no_common,0) -Do not put uninitialized globals in the common section. +Put uninitialized globals in the common section. fcompare-debug Driver
