public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102819] [11/12 Regression] IFN_COMPLEX_MUL matches things that it shouldn't Date: Wed, 02 Feb 2022 10:54:49 +0000 [thread overview] Message-ID: <bug-102819-4-ItHdoyzthi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102819 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:ab95fe61fea38fbac7f4e00abd32c2530532351a commit r12-6994-gab95fe61fea38fbac7f4e00abd32c2530532351a Author: Tamar Christina <tamar.christina@arm.com> Date: Wed Feb 2 10:51:38 2022 +0000 AArch64: use canonical ordering for complex mul, fma and fms After the first patch in the series this updates the optabs to expect the canonical sequence. gcc/ChangeLog: PR tree-optimization/102819 PR tree-optimization/103169 * config/aarch64/aarch64-simd.md (cml<fcmac1><conj_op><mode>4): Use canonical order. * config/aarch64/aarch64-sve.md (cml<fcmac1><conj_op><mode>4): Likewise.
next prev parent reply other threads:[~2022-02-02 10:54 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-18 18:34 [Bug tree-optimization/102819] New: " rsandifo at gcc dot gnu.org 2021-10-18 20:05 ` [Bug tree-optimization/102819] " tnfchris at gcc dot gnu.org 2021-10-19 7:42 ` rguenth at gcc dot gnu.org 2022-02-02 10:54 ` cvs-commit at gcc dot gnu.org 2022-02-02 10:54 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-02 10:54 ` cvs-commit at gcc dot gnu.org 2022-02-02 10:57 ` [Bug tree-optimization/102819] [11 " tnfchris at gcc dot gnu.org 2022-02-25 12:13 ` cvs-commit at gcc dot gnu.org 2022-02-25 12:13 ` cvs-commit at gcc dot gnu.org 2022-02-25 12:13 ` cvs-commit at gcc dot gnu.org 2022-02-25 12:14 ` tnfchris 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-102819-4-ItHdoyzthi@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).