From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3CD403858C52; Thu, 19 Jan 2023 10:29:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3CD403858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674124199; bh=bOqxFfnZg1ITi96blnJmdvmRT3bkSyrBkj2z0V3UVY8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vbBwLh9rBhKI0rfwVokkbyA5i+s1w7ANL7EVNHaxWbWmCFUsKktST41CXqRsntUnx wMt8p7ot3XPfyDqtPzzzqAJ7ajgy1RsZxkpHQwRbDNgbmoCiKPmFqnYcd2d303IIpy rX/NAgBgMFF+XAWz3/ieAxugdxNwiAV8TIWZfb3w= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108447] [13 Regression] glibc math/test-*-iseqsig failures Date: Thu, 19 Jan 2023 10:29:58 +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: missed-optimization, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108447 --- Comment #12 from Jakub Jelinek --- As a workaround in stage4, perhaps, but long term the relations make a lot = of sense even for floating point with NANs. If you know <=3D relation between= 2 vars and know the range of one of them, the other can be computed from it, = ...=