More C type errors by default for GCC 14

Richard Biener richard.guenther@gmail.com
Wed May 10 08:46:02 GMT 2023


On Wed, May 10, 2023 at 10:05 AM Jonathan Wakely via Gcc
<gcc@gcc.gnu.org> wrote:
>
> On Wed, 10 May 2023, 03:32 Eli Zaretskii, <eliz@gnu.org> wrote:
>
> >
> > And then people will start complaining about GCC unnecessarily
> > erroring out, which is a compiler bug, since there's no problem
> > producing correct code in these cases.
> >
>
>
> What is the correct code for this?
>
> void foo(int);
> void bar() { foo("42"); }
>
> Why should this compile?
>
> You keep demanding better rationale for the change, but your argument
> amounts to nothing more than "it compiles today, it should compile
> tomorrow".

void foo(__UINTPTR_TYPE__);
void bar() { foo("42"); }

might be something we'd still like to diagnose but eventually not turn
into an error?  Yes, it then depends on the target whether the code is
accepted or not, but at least it would continue working where there's
a "good" answer to your question.

Probably splitting hairs here ..

Richard.
>
> >


More information about the Gcc mailing list