public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/43687] Unexpected error message for bad command line argument
Date: Thu, 15 Apr 2010 21:43:00 -0000	[thread overview]
Message-ID: <20100415214252.24879.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43687-296@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from manu at gcc dot gnu dot org  2010-04-15 21:42 -------
(In reply to comment #10)
> 
> We haven't determined who will end up implementing the proposal or 
> produced an implementation design at that level of detail, but personally 

You make it sound as a project that will take years to get done.

I just want to know whether my current approach is feasible or will be
overridden by this work, so I don't waste my free time on this.

Basically, group options are marked as such in *.opt and a function pointer is
added for each option. The awk scripts assign the function set_Woption to this
pointer. This function is hand-written right now but in the future it could be
autogenerated. When the option is enabled/disabled, the set_W function is
called.

If you want I can provide a concrete patch.


-- 


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


  parent reply	other threads:[~2010-04-15 21:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 13:27 [Bug driver/43687] New: " joel at gcc dot gnu dot org
2010-04-08 22:35 ` [Bug driver/43687] " pinskia at gcc dot gnu dot org
2010-04-08 22:40 ` pinskia at gcc dot gnu dot org
2010-04-09  7:28 ` manu at gcc dot gnu dot org
2010-04-09 21:34 ` wilson at gcc dot gnu dot org
2010-04-09 22:16 ` wilson at codesourcery dot com
2010-04-15 19:50 ` joseph at codesourcery dot com
2010-04-15 20:01 ` manu at gcc dot gnu dot org
2010-04-15 20:37 ` joseph at codesourcery dot com
2010-04-15 20:53 ` manu at gcc dot gnu dot org
2010-04-15 21:30 ` joseph at codesourcery dot com
2010-04-15 21:43 ` manu at gcc dot gnu dot org [this message]
2010-04-15 22:01 ` joseph at codesourcery dot com
2010-04-15 22:22 ` manu at gcc dot gnu dot org
2010-04-15 22:32 ` joseph at codesourcery dot com
2010-04-15 22:43 ` manu at gcc dot gnu dot org
2010-04-15 23:00 ` joseph at codesourcery dot com
     [not found] <bug-43687-4@http.gcc.gnu.org/bugzilla/>
2011-03-23  0:32 ` jsm28 at gcc dot gnu.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=20100415214252.24879.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).