public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98891] New: [11 regression] Neon logical operations not vectorized in DImode since g:cdfc0e863a03698a80c74896cbdc9f5c8c652e64 Date: Fri, 29 Jan 2021 14:49:34 +0000 [thread overview] Message-ID: <bug-98891-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98891 Bug ID: 98891 Summary: [11 regression] Neon logical operations not vectorized in DImode since g:cdfc0e863a03698a80c74896cbdc9f5c8c652e64 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: clyon at gcc dot gnu.org Target Milestone: --- Since g:cdfc0e863a03698a80c74896cbdc9f5c8c652e64 (r10-2761), I have noticed that vorr/vorn is no longer vectorized in DImode. I am compiling a modified version of gcc/testsuite/gcc.target/arm/neon-vorns64.c with -mfloat-abi=hard -mcpu=cortex-a9 -mfpu=auto -O3: ==================================================== #include "arm_neon.h" #include <stdlib.h> int64x1_t out_int64x1_t = 0; int64x1_t arg0_int64x1_t = (int64x1_t)0xdeadbeef00000000LL; int64x1_t arg1_int64x1_t = (int64x1_t)(~0xdead00000000beefLL); int main (void) { out_int64x1_t = vorn_s64 (arg0_int64x1_t, arg1_int64x1_t); if (out_int64x1_t != (int64x1_t)0xdeadbeef0000beefLL) abort(); return 0; } ==================================================== Before that commit I get: vldr.64 d17, [r3] @ int ... vldr.64 d16, [r3, #8] @ int vorn d16, d16, d17 ... After that commit: ldr lr, [r3] ldr r4, [r3, #8] ldr ip, [r3, #4] ldr r6, [r3, #12] mvn r3, lr orr r0, r4, r3 ... mvn r3, ip orr r1, r6, r3 ... Recent trunk has: ldrd r2, [r1] ldrd r0, [r1, #8] mvn r2, r2 mvn r3, r3 orr r2, r2, r0 ... orr r3, r3, r1
next reply other threads:[~2021-01-29 14:49 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-29 14:49 clyon at gcc dot gnu.org [this message] 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 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@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).