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 3492B3858C5E; Tue, 20 Jun 2023 17:38:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3492B3858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687282692;
	bh=rj9at37oCFaKzNG3cTz+5mRKtgY8k7dp8oP83FgA0KQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hDhQJOwfjhPnDIC+4C10E1dJ3mi+Q6AJ3KMse2oSNijtJRrx579ZvQjor0yHzFHxK
	 1otr2xjlqAp53zbXZT1hUR+S/VsbJENgiPwEm6LHn/v8r5NRiDC5j5p/if8UUvRRis
	 6GWCJSDnJtH2uaB3O8DgMxJo6S1Zj7wdNXhiuGwQ=
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110311] [14 Regression] gfortran 14.0 regression
Date: Tue, 20 Jun 2023 17:38:11 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy 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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110311-4-U8cqNVgj8R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110311-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110311-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=3D110311

--- Comment #5 from J=C3=BCrgen Reuter <juergen.reuter at desy dot de> ---
(In reply to anlauf from comment #4)
> J=C3=BCrgen,
>=20
> I'm afraid we need a reproducer.  Or can you bisect the regression furthe=
r?

In principle, I could. But I just undid this commit of yours which is just =
one
line in trans-array.cc, and that didn't solve the problem. So in the
corresponding period of time between last Monday (June 12) and this week (J=
une
19) there have not been any other commits to gcc/fortran or libgfortran, as=
 far
as I can say. So this seems to be a problem with tree-optimization, maybe.=