public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/31349] [4.3 Regression] gcc -v --help returns no options for C, C++
Date: Tue, 19 Feb 2008 10:36:00 -0000	[thread overview]
Message-ID: <20080219103511.9049.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31349-13350@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from nickc at gcc dot gnu dot org  2008-02-19 10:35 -------
Subject: Bug 31349

Author: nickc
Date: Tue Feb 19 10:33:41 2008
New Revision: 132427

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132427
Log:
        PR other/31349
        * opts.c (undocumented_msg): Leave blank unless checking is
        enabled.
        (handle_options): Fix indentation.
        (print_filtered_help): If no language-specific options were
        displayed tell the user how to list all the options supported by
        the language's front-end.
        (print_specific_help): Fix indentation and remove duplicate line.
        (common_handle_option): Handle the -v option.
        For --help enable the display of undocumented options if the -v
        switch has been included on the command line.
        For --help= check for overlaps in the arguments between the option
        classes and the language names and issue a warning when they
        cannot be disambiguated.
        * c.opt (v): Pass on to the common option handler.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/c.opt
    trunk/gcc/opts.c


-- 


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


  parent reply	other threads:[~2008-02-19 10:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 21:42 [Bug other/31349] New: " brooks at gcc dot gnu dot org
2007-03-25 21:48 ` [Bug other/31349] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-06-29 18:05 ` mmitchel at gcc dot gnu dot org
2007-07-03 10:59 ` nickc at redhat dot com
2007-07-03 16:27 ` nickc at redhat dot com
2007-07-03 19:45 ` brooks at gcc dot gnu dot org
2007-07-03 19:46 ` brooks at gcc dot gnu dot org
2007-07-04 13:40 ` nickc at redhat dot com
2008-01-22  9:04 ` manu at gcc dot gnu dot org
2008-01-23 13:55 ` nickc at redhat dot com
2008-01-23 14:21 ` nickc at redhat dot com
2008-02-19 10:36 ` nickc at gcc dot gnu dot org [this message]
2008-02-19 11:21 ` manu at gcc dot gnu dot org
2008-02-19 14:13 ` nickc at redhat dot com
2008-02-19 14:45 ` manu at gcc dot gnu dot org
2008-02-19 15:12 ` nickc at redhat dot com
2008-02-19 16:15 ` manu 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=20080219103511.9049.qmail@sourceware.org \
    --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).