From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 500983858C83; Mon, 20 Feb 2023 03:57:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 500983858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1676865437; bh=7qLZPuSzqGc3ORyHNZAsoOtK1LgYVBD5SzHd/zCE/zk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JnE8asR1REKBnudOZOi9hj/EW4gbXcwuXqaYHtZpmZkDuZlGujMP/k4gcHOQ17G8F jncd6eR6/hGuKKhvPjJFdiMeLGOCR5MpF+pk9nS1EI6Bi3UDimCCv8f6PrP+VrEgHj yzpv0pgqRHw171sAI0ZxiX22s2M/RdZ1qhzB8lOI= From: "rvmallad at amazon dot com" 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: Mon, 20 Feb 2023 03:57:15 +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: rvmallad at amazon dot com 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=3D107409 --- Comment #20 from Rama Malladi --- @Martin J and @Sebastian P, Let me walk you through the perf data and my triage. First, my triage has been on Graviton 3 (neoverse-v1) processor based instances. Next, I was looking for perf delta going from gcc-7 to gcc-10. I found 2 issues: One was reported in 107413 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107413) and fixed (the perf= delta between gcc-7 and gcc-8 -- 215s vs. 266s); Another one is the issue reporte= d in here. I did another triage and landed at the same commit that I reported earlier. # first bad commit: [a9a4edf0e71bbac9f1b5dcecdcf9250111d16889] Update max_bb_count in execute_fixup_cfg Please let me know any further info/ studies you would like to see on this report. Thank you.=