public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/92455] Unnecessary memory read in a loop Date: Fri, 29 May 2020 07:48:54 +0000 [thread overview] Message-ID: <bug-92455-4-DHPjKRiF3r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92455-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92455 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org --- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> --- I've just run SPEC2006 and SPEC2017 on various machines and I haven't found any speed improvement. There are 2 noticeable regressions: znver2 -Ofast: SPEC/SPEC2017/FP/507.cactuBSSN_r - +5.62% znver2 -Ofast PGO: SPEC/SPEC2017/INT/520.omnetpp_r - +2.42%
next parent reply other threads:[~2020-05-29 7:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92455-4@http.gcc.gnu.org/bugzilla/> 2020-05-29 7:48 ` marxin at gcc dot gnu.org [this message] 2020-05-30 12:10 ` marxin at gcc dot gnu.org 2021-04-27 11:38 ` jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-01-06 4:03 ` pinskia 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-92455-4-DHPjKRiF3r@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).