From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 98DBD3858D39; Tue, 28 Mar 2023 12:25:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 98DBD3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680006324; bh=MkM3LY1g4l8HEZH/a+MK75REqLS1AeXWhUkDmhFVByA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XWGOg/li1KY5gmqCPUO700c/klluwMiqxMfSZZODQee9hMScZaC3gqxiOLjpuoCf5 V+1XUzIlMznwKRmU4zfvar1NruDD1Fs7AvO8fWWTCMImRclIj0Zn/3CoevG50vZ2Pj e3/tEQow0o5gY5qXBUINXNZByxDcMSzQu5swDsb8= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109154] [13 regression] jump threading de-optimizes nested floating point comparisons Date: Tue, 28 Mar 2023 12:25:24 +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 X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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: 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=3D109154 --- Comment #27 from Richard Biener --- I've added heuristics to threading to PR109048 but I think it's too strong = to reject them. For the testcase in this PR ranger could fix up if it managed to properly propagate the singleton range early. After Jakubs change we're still not doing that for unknown reasons. Jakubs later testcase OTOH looks completely different (and more like PR1090= 48).=