From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6031 invoked by alias); 2 Nov 2008 19:12:10 -0000 Received: (qmail 26347 invoked by uid 48); 2 Nov 2008 19:10:47 -0000 Date: Sun, 02 Nov 2008 19:12:00 -0000 Subject: [Bug other/37998] New: Unclear documentation of -fno-common X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dmacks at netspace dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-11/txt/msg00137.txt.bz2 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