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 8801C388F317; Fri, 16 Dec 2022 07:48:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8801C388F317
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1671176904;
	bh=HwFDM+2SX1hErzzMPtHzlr0C7VsMy2SUq7KNQbiP5FY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Rrm+CkZhrFmNgR9H0ub4Sk8I9vHR6FlIlnXpn/ws2y0NXizznGg+2606v87VCYPyp
	 TtPxKl7lXeHKosbKRBhSFeFePi0uPA6+myLAnI1cF4fSqRhGjmGvJIdO8Y5gltxhXT
	 fXIQXWIkWQvwTw/DUsU6YutwcMi5Ul8VpoctySZ4=
From: "burnus at gcc dot gnu.org" <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: Fri, 16 Dec 2022 07:48:23 +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: burnus at gcc dot gnu.org
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-4v9ASpAIkS@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 #16 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Haochen Jiang from comment #15)
> My script shows that this commit cause testcase fail following:
> (It is still running and you might get a email from gcc-regression
> afterwards)
> FAIL: libgomp.fortran/allocate-4.f90   -O   (test for errors, line 19)

Sorry, it looks as if I accidentally committed one file that should not get
committed. (It is part of the pending patch at
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608401.html ) I will
revert it now and keep triple checking next time.

What puzzles me is that the commit hook no longer rejects commits where fil=
es
aren't
listed in the ChangeLog. I will follow up with Martin Li=C5=A1ka and see wh=
y that's
no
longer the case.

Thanks for reporting!=