From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BF4CB3858D1E; Fri, 2 Sep 2022 20:09:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BF4CB3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1662149389; bh=pIumo1GbTvcHWVW95GNR4bWgH/VS+TATYMPuUJCUD8I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QLv7zvgHczPNPcDaMCLDkJYIllxcl0cuw1rcIOO4C5t8aRmdBbvK6HTCl5FV8x+c0 +XRjb1mWqeOaue4PpFD1N7/PZle2NKPsbOKrM7JRlIMMCYOH5I/iNMSpjfTfjYSiFX VZBwl8TCgkvrEDj4sbA3HsICeBb7A95aNDFwTMuY= From: "mikael at gcc dot 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 20:09:49 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106817 --- Comment #4 from Mikael Morin --- (In reply to anlauf from comment #2) > I see: >=20 > D.4225 =3D a + 1; > a =3D {CLOBBER}; > copy (&D.4225, &a); >=20 > so I do not see any failure. With the testcase from comment #3, it becomes: a =3D {CLOBBER}; D.4223 =3D a + 1; copy (&a, &D.4223);=