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/103317] [12 regression] Spec 2017 benchmark blender_r fails with -Ofast on PowerPc (power9, power10) Date: Fri, 19 Nov 2021 11:51:19 +0000 [thread overview] Message-ID: <bug-103317-4-rDF5shC0D8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103317-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103317 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seurer at gcc dot gnu.org --- Comment #14 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 103321 has been marked as a duplicate of this bug. ***
prev parent reply other threads:[~2021-11-19 11:51 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 16:02 [Bug tree-optimization/103317] New: " meissner at gcc dot gnu.org 2021-11-18 16:03 ` [Bug tree-optimization/103317] " meissner at gcc dot gnu.org 2021-11-18 16:22 ` bergner at gcc dot gnu.org 2021-11-18 16:32 ` meissner at gcc dot gnu.org 2021-11-18 16:55 ` bergner at gcc dot gnu.org 2021-11-18 17:10 ` bergner at gcc dot gnu.org 2021-11-18 18:13 ` bergner at gcc dot gnu.org 2021-11-18 18:26 ` pinskia at gcc dot gnu.org 2021-11-18 18:30 ` pinskia at gcc dot gnu.org 2021-11-18 20:51 ` bergner at gcc dot gnu.org 2021-11-18 20:55 ` pinskia at gcc dot gnu.org 2021-11-18 20:56 ` pinskia at gcc dot gnu.org 2021-11-18 23:31 ` [Bug tree-optimization/103317] [12 regression] " pinskia at gcc dot gnu.org 2021-11-19 0:42 ` bergner at gcc dot gnu.org 2021-11-19 1:54 ` pinskia at gcc dot gnu.org 2021-11-19 7:20 ` cvs-commit at gcc dot gnu.org 2021-11-19 7:21 ` pinskia at gcc dot gnu.org 2021-11-19 11:51 ` pinskia at gcc dot gnu.org [this message]
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-103317-4-rDF5shC0D8@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).