public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Andrea Monaco <andrea.monaco@autistici.org>
Cc: gcc@gcc.gnu.org
Subject: Re: No warning about duplicate values in enum
Date: Fri, 10 Mar 2023 08:05:02 -0500	[thread overview]
Message-ID: <ZAsq/jYXCS3XEk7/@redhat.com> (raw)
In-Reply-To: <875yb8u5lp.fsf@autistici.org>

On Fri, Mar 10, 2023 at 01:57:06PM +0100, Andrea Monaco via Gcc wrote:
> 
> In gcc 8.3.0, compiling
> 
> 
> enum
> test
>   {
>     FIRST = 1,
>     SECOND = 1,
>     THIRD = 2
>   };
> 
> int
> main (void)
> {
>   return 0;
> }
> 
> 
> generates no warning even with -Wextra.  That hit me today, because I
> had a large enum with many explicitly assigned constants and I
> accidentally used the same value twice, which is an obvious source of
> problems.

This is https://gcc.gnu.org/PR16186.

Marek


  reply	other threads:[~2023-03-10 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 12:57 Andrea Monaco
2023-03-10 13:05 ` Marek Polacek [this message]
2023-03-11 12:54 Basile Starynkevitch
2023-03-11 16:48 ` Jonathan Wakely
2023-03-13 13:29   ` Marek Polacek
2023-03-13 13:38     ` Basile Starynkevitch

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=ZAsq/jYXCS3XEk7/@redhat.com \
    --to=polacek@redhat.com \
    --cc=andrea.monaco@autistici.org \
    --cc=gcc@gcc.gnu.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).