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 0BB733858C55; Tue, 20 Sep 2022 17:36:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0BB733858C55
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663695401;
	bh=szj44HPgSAM8nDz0uMB18uUnCZth483J+5zZd83lcSw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=aVCQ4depWYyc62XQuPbJvaILuYuvYM15GN+ZCj4Abgw9eFq1Te5Z5igQAapiD1Egc
	 +sAOwevA83khODOz2DJ7oAv5u3Iy8kjsrsTlg6aYcSNQE6LsLWsYM1KvdO6KuwzmkA
	 ETotc7VrQNetfuZ/NOhNudkfUTFI+MS1FxtUTwLs=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/68097] We should track ranges for
 floating-point values too
Date: Tue, 20 Sep 2022 17:36:39 +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: 6.0
X-Bugzilla-Keywords: compile-time-hog, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-68097-4-OtwSNHSY7k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68097-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=3D68097

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>:

https://gcc.gnu.org/g:10d6109fe183d984a0377a7afe2854a0d794ebeb

commit r13-2741-g10d6109fe183d984a0377a7afe2854a0d794ebeb
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Mon Sep 19 09:59:01 2022 +0200

    frange::set_nonnegative should not contain -NAN.

    A specifically nonnegative range should not contain -NAN, otherwise
    signbit_p() would return false, because we'd be unsure of the sign.

            PR 68097/tree-optimization

    gcc/ChangeLog:

            * value-range.cc (frange::set_nonnegative): Set +NAN.
            (range_tests_signed_zeros): New test.
            * value-range.h (frange::update_nan): New overload to set NAN s=
ign.=