public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <richard.guenther@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Thousands of enum warnings building gcc
Date: Tue, 10 Apr 2012 13:56:00 -0000	[thread overview]
Message-ID: <CAFiYyc1OBqZisDST+Ls=APxxnEwNfbe1Nsqufc25TbXHOD1+9w@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLvYHaTXEhS8Fa9KOnn+UXH1tUYphr3JG2bbAmC8q6ZFjw@mail.gmail.com>

On Tue, Apr 10, 2012 at 3:25 PM, NightStrike <nightstrike@gmail.com> wrote:
> On Tue, Apr 10, 2012 at 8:38 AM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> On 10 April 2012 13:11, NightStrike wrote:
>>> Generally speaking, I've tried to help people get us a clean build of
>>> gcc warning-wise for the windows targets.  This has historically been
>>> challenging mainly due to printf.  Kai added a lot of support for
>>> handling whacky windows printfs, and we were doing very well for a
>>> long time.  Currently, however, there are two instances where giant
>>> massive piles of warnings spit out due to enums not being handled in a
>>> switch.  Is this a warning that we could just disable by default for
>>> building gcc?  My builds are filled with this:
>>>
>>>
>>> ../../../../build/gcc/src/gcc/ipa-pure-const.c:458: warning:
>>> enumeration value `BUILT_IN_NONE' not handled in switch
>>
>> Did you need to paste hundreds of lines of the warning to ask the question?
>>
>> Did you try adding -Wno-switch-enum to the build flags?
>
> I was asking if that could be disabled by default, so that it wouldn't
> have to be manually added to the build flags each time, since the
> massive warnings are intentional.

I don't see them.

Richard.

  reply	other threads:[~2012-04-10 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 12:11 NightStrike
2012-04-10 12:38 ` Jonathan Wakely
2012-04-10 13:25   ` NightStrike
2012-04-10 13:56     ` Richard Guenther [this message]
2012-04-10 14:01       ` NightStrike
2012-04-10 14:43         ` Richard Guenther

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='CAFiYyc1OBqZisDST+Ls=APxxnEwNfbe1Nsqufc25TbXHOD1+9w@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=nightstrike@gmail.com \
    /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).