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 75A073858D1E; Fri,  2 Sep 2022 18:59:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 75A073858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1662145154;
	bh=fO/RCGj187aId5D7eLDGv84EJwLjBkVBIxMwMkIXG3Y=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=M8s85eXnPDjrjZYGKkudPc5tjVnXRWetb60Ov9xKV3JYLVjtp4ucOwm4MXxhXuVCw
	 uLkChOga++2Pzg5bT0v8pXHcVBE80Iy4kLKoHCDAxWOapCpuHSQnzKhcuT/PBBrKXT
	 41GNVidNXxVZjrpKH2kd8IAPAYRhys/7svPUXasI=
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106817] clobber ordering problem when an actual
 intent(in) argument depends on the value of an intent(out) argument
Date: Fri, 02 Sep 2022 18:59:14 +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: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikael 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106817-4-2YmpHmAS6t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106817-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=3D106817

--- Comment #1 from Mikael Morin <mikael at gcc dot gnu.org> ---
PR92178 is vaguely related.
The tests are very similar, but that other PR is about allocatables whereas
this one isn=E2=80=99t, so I think they are different.=