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 8A8393858022; Mon, 24 Oct 2022 10:16:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A8393858022
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666606622;
	bh=IR1TY8WMqfVziIub6RZpvcSi2zML16e9qiOTlYnMxw8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=KvwJUPsLnGWXlEhTyTLuOlzfIltaN5ypFK6MjM/j6y+G/d8AgVfxl2RHQC/CaQlYH
	 PbJdnqzV8Mc7mTKDZ9mYyKY7ngd6nVbOT+Dk1W3R8rJutZBVoGTaywy6Rx7FiFoc/A
	 tPS+Ttd3B9OK8GW52rVwyn3Kct/u/cPLwKLVnxVQ=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107365] ICE in verify_range, at
 value-range.cc:726
Date: Mon, 24 Oct 2022 10:16:57 +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: 13.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
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-107365-4-OJ9fVfoHdn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107365-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107365-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=3D107365

--- Comment #3 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:1e9d9ed095df3d064cf9d91d46f3e5426c2a05a7

commit r13-3453-g1e9d9ed095df3d064cf9d91d46f3e5426c2a05a7
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Sun Oct 23 16:51:17 2022 +0200

    Check HONOR_NANS instead of flag_finite_math_only in frange:verify_rang=
e.

    [Jakub and other FP experts, would this be OK, or am I missing
    something?]

    Vax does not seem to have !flag_finite_math_only, but float_type_node
    does not HONOR_NANS.  The check in frange::verify_range dependend on
    flag_finite_math_only, which is technically not correct since
    frange::set_varying() checks HONOR_NANS instead of
    flag_finite_math_only.

    I'm actually getting tired of flag_finite_math_only and
    !flag_finite_math_only discrepancies in the selftests (Vax and rx-elf
    come to mind).  I think we should just test both alternatives in the
    selftests as in this patch.

    We could also check flag_finite_math_only=3D0 with a float_type_node
    that does not HONOR_NANs, but I have no idea how to twiddle
    FLOAT_MODE_FORMAT temporarily, and that may be over thinking it.

            PR tree-optimization/107365

    gcc/ChangeLog:

            * value-range.cc (frange::verify_range): Predicate NAN check in
            VARYING range on HONOR_NANS instead of flag_finite_math_only.
            (range_tests_floats): Same.
            (range_tests_floats_various): New.
            (range_tests): Call range_tests_floats_various.=