public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95401] [10/11 Regression] GCC produces incorrect instruction with -O3 for AVX2 since r10-2257-g868363d4f52df19d Date: Fri, 29 May 2020 07:31:11 +0000 [thread overview] Message-ID: <bug-95401-4-sXR07RBNxC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95401-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95401 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |10.2 Priority|P3 |P2
next prev parent reply other threads:[~2020-05-29 7:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 5:18 [Bug tree-optimization/95401] New: GCC produces incorrect instruction with -O3 for skylake-avx512 vsevolod.livinskij at frtk dot ru 2020-05-29 7:08 ` [Bug tree-optimization/95401] GCC produces incorrect instruction with -O3 for AVX2 rguenth at gcc dot gnu.org 2020-05-29 7:16 ` [Bug tree-optimization/95401] [10/11 Regression] GCC produces incorrect instruction with -O3 for AVX2 since r10-2257-g868363d4f52df19d marxin at gcc dot gnu.org 2020-05-29 7:31 ` rguenth at gcc dot gnu.org [this message] 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-12-30 13:36 ` rsandifo at gcc dot gnu.org 2021-01-05 10:59 ` [Bug tree-optimization/95401] [10 " rsandifo at gcc dot gnu.org 2021-01-12 10:06 ` rsandifo at gcc dot gnu.org 2021-03-05 5:10 ` aoliva at gcc dot gnu.org 2021-03-05 8:03 ` rguenth at gcc dot gnu.org 2021-03-11 7:00 ` aoliva 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-95401-4-sXR07RBNxC@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).