public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97730] [10/11 Regression] aarch64, SVE2: Wrong code since r10-5853-g0a09a948 (wrong pattern for BCAX) Date: Thu, 05 Nov 2020 13:36:03 +0000 [thread overview] Message-ID: <bug-97730-4-mLbHdNoOFF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97730-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97730 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Target Milestone|--- |10.3 Known to fail| |11.0 CC| |rsandifo at gcc dot gnu.org Target| |aarch64
next prev parent reply other threads:[~2020-11-05 13:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-05 13:35 [Bug target/97730] New: " acoplan at gcc dot gnu.org 2020-11-05 13:36 ` acoplan at gcc dot gnu.org [this message] 2020-11-05 13:46 ` [Bug target/97730] " rguenth at gcc dot gnu.org 2020-11-12 10:06 ` cvs-commit at gcc dot gnu.org 2020-11-12 10:08 ` [Bug target/97730] [10 " acoplan at gcc dot gnu.org 2020-11-19 10:47 ` cvs-commit at gcc dot gnu.org 2020-11-19 10:49 ` acoplan 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-97730-4-mLbHdNoOFF@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).