From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4E268395C00F; Mon, 12 Dec 2022 09:07:20 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4E268395C00F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1670836040;
	bh=8/Or3p6vABBrNrlnhfOPEb9JBoS3FWk0+xOzIbxEwzY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=FlLr2yWCJkAMscUz0CB+MSvculTJChxIqqnnhIzw64W3P8msTpc3zE1132sAHyFiz
	 +wS2fHXMujS7eJ60a2m3IWCr0b7Nx3Njyvlw++Fy7/7AlT+vpcN/V8x6glcpiJKaAU
	 95IHKeFaflEVFaAOpsCgG4MmMj75QjlYKrj3rIEc=
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/108056] [12/13 Regression] backward compatibility
 issue between 11 and 12
Date: Mon, 12 Dec 2022 09:07:19 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108056-4-1CHaq2b8Oq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108056-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108056-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108056

--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 12 Dec 2022, jakub at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108056
>=20
> --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> The important question is if correct code compiled by gcc 11 was working
> correctly with libgfortran 11, if yes, then libgfortran 12+ should mainta=
in
> compatibility (of course, when soname is bumped, that compatibility code =
can be
> thrown away).

If GCC 11 behaves incorrectly we can of course also fix that on the=20
branch.  Nevertheless breaking old working executables isn't a good
idea so if we can keep them working then please do so.=