Re: More C type errors by default for GCC 14

Sam James <[email protected]> Tue, 09 May 2023 17:11:21 +0100
Newsgroups dev.linux.lists.c-std-porting
Message-ID <[email protected]>
--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Jakub Jelinek <[email protected]> writes:

> On Tue, May 09, 2023 at 05:16:19PM +0200, Richard Biener via Gcc wrote:
>>=20
>>=20
>> > Am 09.05.2023 um 14:16 schrieb Florian Weimer via Gcc <[email protected]=
>:
>> >=20
>> > =EF=BB=BFTL;DR: This message is about turning implicit-int,
>> > implicit-function-declaration, and possibly int-conversion into errors
>> > for GCC 14.
>>=20
>> I suppose the goal is to not need to rely on altering CFLAGS but change =
the default behavior with still being able to undo this using -Wno-error=3D=
 or -Wno-?
>
> Can't people just compile C89/K&R code with -std=3Dc89/-std=3Dgnu89 and n=
ot get
> these errors that way?

This is what we've been doing for hopeless projects and it's probably my
preference, but I'm fine with Florian's -fpermissive suggestion too.

(The point about inline semantics is important but you can handle that
with other flags anyway.)

best,
sam


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZFpw118UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB
NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv
by5vcmcACgkQc4QJ9SDfkZCCOQD9HOnMyFk+BlDOFLk4v4JrOyPYATE+CGmq2GTO
rbvqfGcBAKSKr7roTiYUKUL1KCXPbSlGXIPa0QLt6yx8IonGnnAN
=b825
-----END PGP SIGNATURE-----
--=-=-=--