public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94373] New: 548.exchange2_r run time is 7-12% worse than GCC 9 at -O2 and generic march/mtune Date: Fri, 27 Mar 2020 21:49:19 +0000 [thread overview] Message-ID: <bug-94373-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94373 Bug ID: 94373 Summary: 548.exchange2_r run time is 7-12% worse than GCC 9 at -O2 and generic march/mtune Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: jamborm at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Blocks: 26163 Target Milestone: --- Host: x86_64-linux Target: x86_64-linux When compiled with just -O2, SPEC 2017 INTrate benchmark 548.exchange2_r runs slower than when compiled with GCC 9.2. It is: - 8% slower on AMD Zen2-based server CPU (rev. 26b3e568a60) - 12% slower on Intel Cascade Lake server CPU (rev. abe13e1847f) - 7% slower on AMD Zen1-based server CPU (rev. 26b3e568a60) During GCC 10 development cycle the benchmark was relatively noisy and the run time was increasing in many small steps, but between October 7 and November 15 we were doing 3% better than GCC 9 (on Zen2). Specifically the following commit brought about the improvement: commit 806bdf4e40d31cf55744c876eb9f17654de36b99 Author: Richard Biener <rguenther@suse.de> Date: Mon Oct 7 07:53:45 2019 +0000 re PR tree-optimization/91975 (worse code for small array copy using pointer arithmetic than array indexing) 2019-10-07 Richard Biener <rguenther@suse.de> PR tree-optimization/91975 * tree-ssa-loop-ivcanon.c (constant_after_peeling): Consistently handle invariants. From-SVN: r276645 But it was undone by its revert: commit f0af4848ac40d2342743c9b16416310d61db85b5 Author: Richard Biener <rguenther@suse.de> Date: Fri Nov 15 09:09:16 2019 +0000 re PR tree-optimization/92039 (Spurious -Warray-bounds warnings building 32-bit glibc) 2019-11-15 Richard Biener <rguenther@suse.de> PR tree-optimization/92039 PR tree-optimization/91975 * tree-ssa-loop-ivcanon.c (constant_after_peeling): Revert previous change, treat invariants consistently as non-constant. (tree_estimate_loop_size): Ternary ops with just the first op constant are not optimized away. * gcc.dg/tree-ssa/cunroll-2.c: Revert to state previous to unroller adjustment. * g++.dg/tree-ssa/ivopts-3.C: Likewise. From-SVN: r278281 On the Intel machine, reverting the revert fixes the regression too. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163 [Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
next reply other threads:[~2020-03-27 21:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-27 21:49 jamborm at gcc dot gnu.org [this message] 2020-03-27 22:06 ` [Bug target/94373] " pinskia at gcc dot gnu.org 2020-03-30 5:09 ` crazylht at gmail dot com 2020-03-30 6:26 ` crazylht at gmail dot com 2020-03-30 7:59 ` rguenth at gcc dot gnu.org 2021-02-04 17:15 ` [Bug target/94373] 548.exchange2_r run time is 16-35% " jamborm at gcc dot gnu.org 2023-01-18 16:57 ` jamborm at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-94373-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).