From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 942F03858C5E; Tue, 20 Feb 2024 14:02:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 942F03858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1708437767; bh=CTUIAD1XVJZMkW3LxW5MxAYBJxY98FJWboO4R5/9pOc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KsvA3yB8JodDGzRjQ1AiIMLK56ZqJtoZB9UT6GTKw/Iw2036G+rnh/+ptMA8zvefB hB1FeQCkmpSjzHgM3/F57gfiwq4yGdzelm4Vdh2lhLWQWM40PkWSzLCCWVVVmvgkWB CcbxFnF53sAnwlNXD1WE8K4WzUY2qFMPNjLJveaY= From: "jamborm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112312] -O3 produces worse code than -O2 for std::ranges::lower_bound in some cases, not marking a loop as finite Date: Tue, 20 Feb 2024 14:02: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: 14.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm 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: 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=3D112312 --- Comment #4 from Martin Jambor --- It seems this has been fixed in current master (which is to become gcc 14). If my bisecting is correct, it has been fixed by r14-5628-g53ba8d669550d3 (= Jan Hubicka: inter-procedural value range propagation). I guess it would be nice to add this testcase to the testsuite, so I'm keep= ing this bug opened (and on my TODO list).=