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 B52083858C3A; Fri, 23 Jun 2023 23:23:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B52083858C3A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687562597;
	bh=1Gqd9dkGH8Oc8lLbhLlIpOl0wzknsWPvdvhYYmG9daA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=eC9gNkWYx3kYp67XE258l1gd0lo70vKg0IabUHPm69BW5w64LzmWmPkuStkG9zp1p
	 TvwhTUsByGYRiQWNrYKnwv3y3ZgoOl8Xyznywmrdn6+wCB0cAJgpZ5cD9dxIItYEwP
	 LVQbmx3K2wlV5hHYZxtf5ihv9PCE65TxFE1YnVBg=
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110311] [14 Regression] regression in tree-optimizer
Date: Fri, 23 Jun 2023 23:23:17 +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-ShGUq44GaR@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 #12 from J=C3=BCrgen Reuter <juergen.reuter at desy dot de> ---
Any idea which commit could cause such an issue? At least I now understand =
that
in our program the random number object gets undefined and produces NaNs.=