public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98891] [10/11 regression] Neon logical operations not vectorized in DImode since g:cdfc0e863a03698a80c74896cbdc9f5c8c652e64 Date: Wed, 17 Mar 2021 12:58:49 +0000 [thread overview] Message-ID: <bug-98891-4-gVwBz5YSpd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98891-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98891 --- Comment #3 from Wilco <wilco at gcc dot gnu.org> --- Older GCCs only ever did this for vorn, not for other operations like add/sub/and/orr/eor, so current behaviour is now fully consistent, and I don't consider it a bug. One could argue these intrinsics should always map to Neon instructions rather than being optimized into 64-bit integer operations. However GCC never did support this except for vorn, so it's not clear whether there is an advantage in changing this now.
next prev parent reply other threads:[~2021-03-17 12:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-29 14:49 [Bug target/98891] New: [11 " clyon at gcc dot gnu.org 2021-01-29 16:14 ` [Bug target/98891] " rguenth at gcc dot gnu.org 2021-02-26 11:53 ` [Bug target/98891] [10/11 " rguenth at gcc dot gnu.org 2021-03-17 9:37 ` jakub at gcc dot gnu.org 2021-03-17 9:39 ` jakub at gcc dot gnu.org 2021-03-17 12:58 ` wilco at gcc dot gnu.org [this message] 2021-03-17 13:09 ` wilco at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-08 12:10 ` wilco 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-98891-4-gVwBz5YSpd@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).