From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 05F953858CDA; Mon, 27 Mar 2023 09:44:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 05F953858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679910288; bh=q/+f0sU5/JZ1KjrXDaparyVscYyLxs1DDUjqB2Itmac=; h=From:To:Subject:Date:In-Reply-To:References:From; b=E/1opHYAxf4+mzI43xe7HCRvxGu+jSWkeRDydvkU5wir3tpZ2+FqkgzwrnRd1WyGs 7xh0NSoZhnoSYe9B5cjw+FRpGH8OMEm1tncM7ihC/Hs+inCbbeqWP4OodV0XtQR2SI 0nTLdeuLTUwpc30xbFYkQZ3MEdeWfjAqtc8yjl4Q= From: "jakub 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: Mon, 27 Mar 2023 09:44:47 +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: jakub 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 #14 from Jakub Jelinek --- (In reply to Jakub Jelinek from comment #12) > We definitely should add range-ops for conversions from integral to float= ing > point and from floating to integral and their reverses. Do we have range-ops for floating to floating point conversions btw (float = to double or vice versa etc.)? If not, that is something to implement too for GCC 14.=