This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/43687] Unexpected error message for bad command line argument
- From: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Apr 2010 21:42:52 -0000
- Subject: [Bug driver/43687] Unexpected error message for bad command line argument
- References: <bug-43687-296@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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