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 5ACFA3882AC1; Fri, 30 Jun 2023 21:09:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5ACFA3882AC1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688159388;
	bh=tWJAkmpkXvppgTL1H4Fv4oOouAYQQbvUq+AWN/4JcBM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UKG2wCdZCSqMiiTbPmoRo3MAT9YnPFIykJ6zbzj7zkKHSkFPz5mTDGCty6rYo88ed
	 ujGLyZ9v5ws9Mr1nAObu2PQ9YG70lAtcfg/YJO5MVUf9EJHAf+zgEkhE2QrvbUMMeh
	 zwAov/+Ayi5uRNNuFfRC78+7kC756HBHTE3Z6pIw=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110311] [14 Regression] regression in
 tree-optimizer
Date: Fri, 30 Jun 2023 21:09:48 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110311-4-s4vDe7gFhP@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 #41 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Uro=C5=A1 Bizjak from comment #39)
> (In reply to anlauf from comment #36)
> > Breakpoint 2, rng_stream.rng_stream_s::mmm_mod (x1=3D330289839997,
> > x2=3D4294967087) at rng_stream_sub.f90:336
> > 336         res =3D mod (x1, x2)
> > (gdb) info float
> >   R7: Valid   0x401be51fb57800000000 +480507567=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20
> >   R6: Valid   0x401be51fb57800000000 +480507567=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20
> >   R5: Zero    0x00000000000000000000 +0=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >   R4: Zero    0x00000000000000000000 +0=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >   R3: Zero    0x00000000000000000000 +0=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >   R2: Zero    0x00000000000000000000 +0=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> >   R1: Zero    0x00000000000000000000 +0=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
> > =3D>R0: Special 0xffff0000000004f5dc90 Unsupported

0xffff0000000004f5dc90 is pseudo NaN:
Pseudo Not a Number. The sign bit is meaningless. The 8087 and 80287 treat =
this
as a Signaling Not a Number. The 80387 and later treat this as an invalid
operand.
So, if that comes from some random number generator, I'd say that random nu=
mber
generator should be fixed not to create the erroneous cases for
https://en.wikipedia.org/wiki/Extended_precision=