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 724FE3858407; Wed, 20 Sep 2023 19:48:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 724FE3858407
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1695239294;
	bh=FDjZS3WPecXX0hLBOnAq+ZigLOqxww8Fuk3EGmLBF6I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=B72CpFLjloPapim20bqofqeA7ZSYt7ZmyY43Ppj8lWq4q5G5CrVuOkPMHatpGR+1m
	 qiWVXQHtsz1yEqY2DlfoPsOlMGeDAJ+MtJX1aD1CXgUuyIh5jbAWIC7DCOGkm/yC9r
	 DxnQb3kV9O3wD3pzLuUzX6MT2WZLnEElcMApSZ2s=
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107716] Getting negative values with NINT when using
 doubleprecision values in range on i386
Date: Wed, 20 Sep 2023 19:48: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: 11.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107716-4-odNAGVCPFw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107716-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107716-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=3D107716

--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> -=
--
On Wed, Sep 20, 2023 at 07:07:37PM +0000, mikael at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107716
>=20
> --- Comment #5 from Mikael Morin <mikael at gcc dot gnu.org> ---
> (In reply to kargl from comment #4)
> > What the heck does "RESOLVED MOVED"?
>=20
> I think it means this PR is not a gcc bug and the problem is tracked on s=
ome
> other project's bug tracker (it is "moved" there).
>=20
> Not sure where else the problem is tracked in this case.
>=20

Thanks, Mikael.  After a bit of duck-duck-go, I've come to a
similar conclusion.

<$0.02>
If a url/pointer to where the bug is actually tracked is not available,
this status should not be used.  It is useless.  I'll also note that if
one clicks on the 'status:' label a list of stati (statuses?) and their
meaining can be found.  MOVED is not among the list.
</$0.02>=