From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 699F43858C53; Thu, 2 Feb 2023 21:35:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 699F43858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675373748; bh=6osr10Hj49QvN/G/Zw2t0BJaVZYzQ9j2D/etnfPIxKg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=G28fI0/d8o/ZMXt2OGKOGu7aQN7QiEoVY60+gA6ogMDQV8dkgbd/vdHxsIkTDqhFQ dP8Pp7k6D+gk00HaBwcwLjzlnv5SQncKBkO6rAIAgK9oxM5YnkdGr3jVjlAihKI1Oe lBZ7DJMcRc0wIZ+tYm1rZs0qL6elEBylqhgqQ4Aw= From: "spop at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107409] Perf loss ~5% on 519.lbm_r SPEC cpu2017 benchmark with r10-5090-ga9a4edf0e71bba Date: Thu, 02 Feb 2023 21:35: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: spop 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: cc 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=3D107409 Sebastian Pop changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |spop at gcc dot gnu.org --- Comment #18 from Sebastian Pop --- A new 5% regression happened in gcc-trunk more recently and may be due to another patch. Rama was bisecting a 15% perf regression on lbm when updating gcc-7 to gcc-= 10. The regression can be seen on the LNT graph link from comment#3=20 https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=3D633.477.0&plot.1= =3D683.477.0&plot.2=3D664.477.0&plot.3=3D648.477.0&plot.4=3D618.477.0&plot.= 5=3D605.477.0&plot.6=3D759.477.0&plot.7=3D584.477.0 gcc-6 has execution time of 213 seconds gcc-7 is at 215 seconds gcc-8 is at 266 gcc-9 at 259 gcc-10 at 260 Honza's patch seems to be unrelated as it was committed to trunk before gcc= -10 release on May 7, 2020: commit a9a4edf0e71bbac9f1b5dcecdcf9250111d16889 Author: Jan Hubicka Date: Sat Nov 30 22:25:24 2019 +0100 Update max_bb_count in execute_fixup_cfg We need to git-bisect between gcc-7 and gcc-8.=