public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: Andrea Monaco <andrea.monaco@autistici.org>
Cc: gcc@gcc.gnu.org
Subject: No warning about duplicate values in enum
Date: Sat, 11 Mar 2023 13:54:39 +0100	[thread overview]
Message-ID: <7785d160-cd05-01e2-e800-4bc82d630c4e@starynkevitch.net> (raw)

Hello all,


Andrea observed that:

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.

I believe that the C standard (which I don't have here, but see also https://port70.net/~nsz/c/c11/n1570.html or buy it from ISO) explicitly allow duplicate values in enum.

For readability of some weird code, or in the case of C code generated by other tools.

By the way, gcc version 12.2.0 (Debian 12.2.0-14) don't emit any warnings neither when used on your example as gcc -Wall -Wextra -fanalyzer /tmp/andrea.c -o /tmp/andrea

If you really want to get warnings, consider writing your GCC plugin (perhaps starting with https://github.com/bstarynk/bismon/ ....) or using static analysis tools like https://frama-c.com/

Regards.

NB my pet open source project is the RefPerSys open source inference engine (work in progress) on http://refpersys.org/

-- 
Basile Starynkevitch <basile@starynkevitch.net>
92340 Bourg-la-Reine, France
http://starynkevitch.net/Basile/ and http://refpersys.org/


             reply	other threads:[~2023-03-11 12:53 UTC|newest]

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

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=7785d160-cd05-01e2-e800-4bc82d630c4e@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --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).