public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brooks at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/31352]  New: gcc -v --help doesn't notice when front-ends documentation differs for same option
Date: Sun, 25 Mar 2007 22:07:00 -0000	[thread overview]
Message-ID: <bug-31352-13350@http.gcc.gnu.org/bugzilla/> (raw)

When an option is present in multiple front ends, the gcc -v --help output
assumes that the documentation is the same in all of the front ends for which
the option is present, and only reports the documentation string for the first
front end for which it appears.

For example, in 4.2, the Ada output has
-------------------------------
  -Wall                       This switch lacks documentation
-------------------------------
and then, in the C output, we have
-------------------------------
  -I, -Wall, -Wlong-long, -Wmissing-format-attribute, -Wmissing-prototypes,
-------------------------------
rather than giving the documentation string for -Wall that's present in c.opt.

Currently, I _think_ this is only affecting the Ada options that lack
documentation (and are thus bug #31351), but it seems unfortunate for the
future as well, since some options may have different interpretations in
different langauges.


-- 
           Summary: gcc -v --help doesn't notice when front-ends
                    documentation differs for same option
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: brooks at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31352


                 reply	other threads:[~2007-03-25 22:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-31352-13350@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: link
Be 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).