This is the mail archive of the
mailing list for the GCC project.
Re: [warnings] tagging warnings about options themselves
- From: Ian Lance Taylor <ian at airs dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: 21 Jul 2005 21:04:30 -0700
- Subject: Re: [warnings] tagging warnings about options themselves
- References: <200507220158.j6M1wo1E025655@greed.delorie.com>
DJ Delorie <email@example.com> writes:
> Also, I was thinking about messages like these:
> warning (0, "command line option \"%s\" is valid for %s but not for %s",
> text, ok_langs, bad_lang);
> warning (0, "switch %qs is no longer supported", option->opt_text);
> warning (0, "unrecognized gcc debugging option: %c", c);
> How about a -Woptions warning?
You mean, an option to control whether the compiler warns about
options? Personally I think this is going a bit overboard. I can see
the advantage to being able to control every warning which can be
produced by source code. But these are bring produced based solely on
the command line and, I suppose, the specs file. I don't think we
need an option to control warnings about what options you use. But
maybe I'm missing something.