Re: More C type errors by default for GCC 14

[Eli Zaretskii <eliz@gnu.org>]

> From: Neal Gompa <neal@gompa.dev>
> Date: Wed, 10 May 2023 08:10:48 -0400
> Cc: sam@gentoo.org, egall@gwmail.gwu.edu, jwakely.gcc@gmail.com, 
> 	joel@rtems.org, dje.gcc@gmail.com, jakub@redhat.com, arsen@aarsen.me, 
> 	gcc@gcc.gnu.org, c-std-porting@lists.linux.dev
> 
> On Wed, May 10, 2023 at 8:05 AM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > From: Neal Gompa <neal@gompa.dev>
> > > Date: Wed, 10 May 2023 06:56:32 -0400
> > > Cc: Eric Gallager <egall@gwmail.gwu.edu>, Jonathan Wakely <jwakely.gcc@gmail.com>, joel@rtems.org,
> > >       David Edelsohn <dje.gcc@gmail.com>, Eli Zaretskii <eliz@gnu.org>, Jakub Jelinek <jakub@redhat.com>,
> > >       Arsen Arsenović <arsen@aarsen.me>, gcc@gcc.gnu.org,
> > >       c-std-porting@lists.linux.dev
> > >
> > > Right, we've been going through a similar effort with C++ over the
> > > past decade. GCC incrementally becoming more strict on C++ has been an
> > > incredibly painful experience, and it eats away a ton of time that I
> > > would have spent dealing with other problems. Having one big event
> > > where the majority of changes to make the C compiler strict happen
> > > will honestly make it less painful, even if it doesn't seem like it at
> > > the moment.
> >
> > But not having such an event, ever, would be even less painful.
> 
> That's not going to happen.

Well, I hope it will.  Otherwise I wouldn't be partaking in this
discussion.