From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2413817FFC
	for <c-std-porting@lists.linux.dev>; Tue,  9 May 2023 16:12:11 +0000 (UTC)
References: <877cth66qb.fsf@oldenburg.str.redhat.com>
 <97CCB305-9ECD-4B3C-B13E-4F2790FE0543@gmail.com> <ZFpvSZPGI+YtTKJw@tucnak>
User-agent: mu4e 1.10.3; emacs 29.0.90
From: Sam James <sam@gentoo.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>, Florian Weimer
 <fweimer@redhat.com>, gcc@gcc.gnu.org, c-std-porting@lists.linux.dev
Subject: Re: More C type errors by default for GCC 14
Date: Tue, 09 May 2023 17:11:21 +0100
In-reply-to: <ZFpvSZPGI+YtTKJw@tucnak>
Message-ID: <87y1lxjxgo.fsf@gentoo.org>
Precedence: bulk
X-Mailing-List: c-std-porting@lists.linux.dev
List-Id: <c-std-porting.lists.linux.dev>
List-Subscribe: <mailto:c-std-porting+subscribe@lists.linux.dev>
List-Unsubscribe: <mailto:c-std-porting+unsubscribe@lists.linux.dev>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha512; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Jakub Jelinek <jakub@redhat.com> 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 <gcc@gcc.gnu.org=
>:
>> >=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-----
--=-=-=--