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/31349] [4.3 Regression] gcc -v --help returns no options for C, C++
Date: Tue, 03 Jul 2007 19:45:00 -0000	[thread overview]
Message-ID: <20070703194501.16229.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31349-13350@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from brooks at gcc dot gnu dot org  2007-07-03 19:45 -------
Nick -

So, if I understand correctly: all of the options are listed somewhere, but we
no longer provide any information about which of the shared options under 
"language related options" are supported by a given language's front end?

While this may have been intentional, I do not think it counts as a feature --
the listing of the "common" options without definitions at the top of the
option listing did not take up a significant amount of space, and it provided
very useful information that's now not absent.

(On the other hand, moving the _descriptions_ of the shared options to a single
listing is a good thing, IMO -- I want to make it clear that I'm not objecting
to the bulk of this change!)


-- 


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


  parent reply	other threads:[~2007-07-03 19:45 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 [this message]
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
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=20070703194501.16229.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).