public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "martinrb at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/37786] New: Documentation for `-symbolic' needs fixing Date: Thu, 09 Oct 2008 18:54:00 -0000 [thread overview] Message-ID: <bug-37786-16725@http.gcc.gnu.org/bugzilla/> (raw) gcc has flags -Bsymbolic and -Bsymbolic-functions which are documented in the usage message. $ gcc -v --help 2>&1 | grep symbolic -Bsymbolic Bind global references locally -Bsymbolic-functions Bind global function references locally However, the info pages are incorrect and incomplete. `-symbolic' Bind references to global symbols when building a shared object. Warn about any unresolved references (unless overridden by the link editor option `-Xlinker -z -Xlinker defs'). Only a few systems support this option. In fact, gcc does not appear to support any such flag `-symbolic'. `-symbolic' should probably be changed to `-Bsymbolic'. Also, please add info documentation for `-Bsymbolic-functions'. A motivating example for these options would be nice as well. (or maybe a link to any corresponding binutils documentation) -- Summary: Documentation for `-symbolic' needs fixing Product: gcc Version: 4.2.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: martinrb at google dot com GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37786
next reply other threads:[~2008-10-09 18:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-09 18:54 martinrb at google dot com [this message] 2008-10-09 18:58 ` [Bug driver/37786] " pinskia at gcc dot gnu dot org 2008-10-09 19:02 ` pinskia at gcc dot gnu dot org 2008-10-09 19:28 ` martinrb at google dot com 2008-10-09 20:36 ` pinskia at gcc dot gnu dot org 2008-10-09 23:11 ` martinrb at google dot com 2008-10-09 23:17 ` pinskia at gcc dot gnu dot org 2008-10-09 23:18 ` martinrb at google dot com
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-37786-16725@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).