From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 19704384CB87; Thu, 14 Mar 2024 16:32:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 19704384CB87 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710433967; bh=q0+rd6eeZdgtDpZUKYpbwoY3CSXRzlbvmgsXvD/7bNo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hWD9QZtBtCBFz58gQDGKOQeXrK6Se/UTT0j4WcxcErQjBp0mtpfdIiBM+wBeYzWb/ DKXrCgKbW3zZf4yX6K3IIMSl0S5ESOc+2mZyGaOikhI37C92fREnm6rZsxjb6JsHU6 U9UJIBy6NKNkarMYta8X8gzPpeqk5HZWqM6nivNU= From: "rdapp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112548] [14 regression] 5% exec time regression in 429.mcf on AMD zen4 CPU (since r14-5076-g01c18f58d37865) Date: Thu, 14 Mar 2024 16:32:46 +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: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rdapp at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 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=3D112548 --- Comment #18 from Robin Dapp --- Hmm, doesn't help unfortunately. A full command line for me looks like: x86_64-pc-linux-gnu-gcc -c -o pbeampp.o -DSPEC_CPU -DNDEBUG -DWANT_STDC_PR= OTO=20 -Ofast -march=3Dznver4 -mtune=3Dznver4 -flto=3D32 -g -fprofile-use=3D/tmp -SPEC_CPU_LP64 pbeampp.c. Could you verify if it's exactly the same for you? Maybe it would also hel= p if you explicitly specified znver4?=