public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101909] [12 Regression] 73% regression on tfft benchmark for -O2 -ftree-loop-vectorize compared to -O2 on zen hardware Date: Mon, 07 Mar 2022 21:30:14 +0000 [thread overview] Message-ID: <bug-101909-4-EWxLDsbDrt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101909-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101909 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.0 Summary|73% regression on tfft |[12 Regression] 73% |benchmark for -O2 |regression on tfft |-ftree-loop-vectorize |benchmark for -O2 |compared to -O2 on zen |-ftree-loop-vectorize |hardware |compared to -O2 on zen | |hardware
next prev parent reply other threads:[~2022-03-07 21:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-14 14:29 [Bug middle-end/101909] New: " hubicka at gcc dot gnu.org 2021-08-16 9:08 ` [Bug tree-optimization/101909] " rguenth at gcc dot gnu.org 2021-08-16 9:17 ` hubicka at ucw dot cz 2021-08-16 9:24 ` marxin at gcc dot gnu.org 2021-08-16 9:56 ` rguenther at suse dot de 2021-08-17 1:42 ` crazylht at gmail dot com 2022-03-07 21:30 ` pinskia at gcc dot gnu.org [this message] 2022-05-06 8:30 ` [Bug tree-optimization/101909] [12/13 Regression] " jakub at gcc dot gnu.org 2023-05-08 12:22 ` [Bug tree-optimization/101909] [12/13/14 " rguenth 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-101909-4-EWxLDsbDrt@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).