public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmacks at netspace dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/37998] New: Unclear documentation of -fno-common Date: Sun, 02 Nov 2008 19:12:00 -0000 [thread overview] Message-ID: <bug-37998-16898@http.gcc.gnu.org/bugzilla/> (raw) 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
next reply other threads:[~2008-11-02 19:12 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-02 19:12 dmacks at netspace dot org [this message] 2009-05-17 13:42 ` [Bug c/37998] " fxcoudert at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-37998-16898@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).