From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BB0CF3858C5E; Tue, 30 Jan 2024 10:25:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB0CF3858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706610342; bh=iorYxG5GxDr48DkkwkoX8cI8l7tQA9Te0T6LnnZVXMg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rHAyB9xm2CG6JpwBi015jmwRQZ7Mnpf+FxVZ3hhJV9bL5UQAvcgEwwOiOBDM4UbVB ae8HbLe2v8fX8j6KyrJ3Vqwtn70Ka1T+2FHY6+77vFdbgjVZ1lOxZ7Xc4l306nExa7 nLrCWIQjUFACA2HldlPDP+rrLh6t8dIO5ZBIrx5g= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113059] [14 regression] fftw fails tests for -O3 -m32 -march=znver2 since r14-6210-ge44ed92dbbe9d4 Date: Tue, 30 Jan 2024 10:25:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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: 14.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=3D113059 --- Comment #17 from Richard Biener --- (In reply to Jakub Jelinek from comment #16) > The question is revert what exactly? > If we revert r14-6210, we get back the other P1. Or do you mean revert > r14-5355? > I guess another option is move the vzeroupper pass one pass later, i.e. > after pass_gcse. I think moving mdreorg passes as late as possible esp. when they don't play well with DF/notes is a good thing. Maybe even after pass_rtl_dse2 and thus after shrink-wrapping?=