From: Eljay Love-Jensen <eljay@adobe.com>
To: Scott Lamb <slamb@slamb.org>, gcc-help@gcc.gnu.org
Subject: Re: Upgrade "may not respond to" warning to error
Date: Mon, 30 Aug 2004 16:01:00 -0000 [thread overview]
Message-ID: <6.1.2.0.2.20040830065939.01f64ec0@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <2ECF1286-F94D-11D8-8E7F-000A95891440@slamb.org>
Hi Scott,
>What's the flag for this message?
I'm not sure. (I haven't familiarized myself with Objective-C. Which is
ironic, since I'm an OS X person.)
Refer to ...
http://gcc.gnu.org/onlinedocs/gcc-3.4.1/gcc/Objective-C-Dialect-Options.html
http://gcc.gnu.org/onlinedocs/gcc-3.4.1/gcc/Warning-Options.html
>Is it possible to do something like -Werror on just some warnings?
No. It's possible to doing something similar, using one of three different
strategies:
1) edit the GCC source code and make the identified warnings
errors. Rebuild your custom GCC.
2) post-process the output (using sed, for instance) and "upgrade" warnings
to errors. Not quite the same thing, doesn't abort the compile, but may be
"good enough". You can use that in conjunction with grep to detect for the
upgraded warnings, and abort a make file by returning a failing error code.
3) have your build process perform two passes. The first pass enables all
the warnings you want to see, the second pass enable only the warnings you
want to be elevated to errors and turn on the -Werror flag.
Those are just a few ideas off the top of my head.
HTH,
--Eljay
prev parent reply other threads:[~2004-08-30 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 6:44 Scott Lamb
2004-08-30 16:01 ` Eljay Love-Jensen [this message]
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=6.1.2.0.2.20040830065939.01f64ec0@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=slamb@slamb.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).