On 3/13/23 14:29, Marek Polacek wrote:
On Sat, Mar 11, 2023 at 04:48:14PM +, Jonathan Wakely via Gcc wrote:
On Sat, 11 Mar 2023, 12:53 Basile Starynkevitch,
wrote:
Hello all,
Andrea observed that:
In gcc 8.3.0, compiling
enum
test
{
FIRST = 1,
SECOND = 1,
THIR
On Sat, Mar 11, 2023 at 04:48:14PM +, Jonathan Wakely via Gcc wrote:
> On Sat, 11 Mar 2023, 12:53 Basile Starynkevitch,
> wrote:
>
> > Hello all,
> >
> >
> > Andrea observed that:
> >
> > In gcc 8.3.0, compiling
> >
> >
> > enum
> > test
> >{
> > FIRST = 1,
> > SECOND = 1,
> >
On Sat, 11 Mar 2023, 12:53 Basile Starynkevitch,
wrote:
> 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 -We
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/
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, be
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,
