From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 75C313858CDB; Sat, 20 Apr 2024 23:03:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 75C313858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1713654212; bh=gTrSwSC4Y1xK49pfj4JDq7qT4pKHPODe503NsLHrmgQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Fm9c8DMn17PitzguaRXQG8+L9XDxCK85ne1NPuj3sGK/Q3rXh1P07zhUXTaig1eaC tw/aWwu4QdNOfGlg647enIq1Esmbx0m4Po9wCWrnzSCAxCUpE+u79056u/pVNVzBSv 8/aOBadX5pdW9Tamhq6SspIS7NuJq6fXfP183HEM= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114787] [14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs) Date: Sat, 20 Apr 2024 23:03:31 +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: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component 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=3D114787 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |tree-optimization --- Comment #3 from Andrew Pinski --- (In reply to Andrew Pinski from comment #2) > The first difference besides prediction/counts on the BB is in the regist= er > allocator. >=20 > The code for aarch64 looks ok too. So I was wrong (and now even more confused than before). In that sometimes = even GCC 13.2.0 code generation is broken. But I don't understand what the conditions are which cause it (adding -fdump-tree-optimized-all or something like that seems to cause different code generation).=