public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Love-Jensen <eljay@adobe.com>
To: Erik <sigra@home.se>, MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: -Werror for certain warnings?
Date: Wed, 08 Nov 2006 12:34:00 -0000	[thread overview]
Message-ID: <C1772AA9.18FD5%eljay@adobe.com> (raw)
In-Reply-To: <455156B4.5090607@home.se>

Hi Erik,

> How is [treating specific warnings as errors] supposed to be done?

Enable just the warnings you want to be treated as errors and use the
-Werror switch.

I do not believe* there is the ability to promote specific warnings (other
than -Werror-implicit-function-declaration) to be treated as errors.

That would be a nice enhancement to GCC.

HTH,
--Eljay

* Always the possibility that I may be mistaken.

  reply	other threads:[~2006-11-08 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08  4:01 Erik
2006-11-08 12:34 ` John Love-Jensen [this message]
2006-11-10  3:40   ` David Fang

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=C1772AA9.18FD5%eljay@adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=sigra@home.se \
    /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).