The gcc.1 manpage states:
>-fno-common
> In C, allocate even uninitialized global variables in the data sec-
> tion of the object file, rather than generating them as common
> blocks. This has the effect that if the same variable is declared
> (without "extern") in two different compilations, you will get an
> error when you link them.
That description is confusing because it's unclear which of the two opposite
situations in the first sentence is the antecedent of the "This" in the second
sentence. Alternative and clearer wordings for second sentence could be:
> If the same variable is declared (without "extern") in two
> different compilations and is allocated in the common blocks, you
> will get an error when you link them due to multiple allocations of
> the same global symbol.
--
Summary: Unclear documentation of -fno-common
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dmacks at netspace dot org
GCC build triplet: powerpc-apple-darwin8.11.0
GCC host triplet: powerpc-apple-darwin8.11.0
GCC target triplet: powerpc-apple-darwin8.11.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37998
