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/100572] New: arm: Assemble failures with MVE vcreateq intrinsic Date: Wed, 12 May 2021 19:51:00 +0000 [thread overview] Message-ID: <bug-100572-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100572 Bug ID: 100572 Summary: arm: Assemble failures with MVE vcreateq intrinsic Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- GCC's output fails to assemble for the following: $ cat test.c #include <arm_mve.h> uint64x2_t v; void f(void) { v = vcreateq_u64(0, 0); } $ ./arm-eabi-gcc -c test.c -march=armv8.1-m.main+mve -mfloat-abi=hard -O /tmp/ccXeZkHP.s: Assembler messages: /tmp/ccXeZkHP.s:31: Error: General purpose registers may not be the same -- `vmov q3[2],q3[0],r2,r2' /tmp/ccXeZkHP.s:32: Error: General purpose registers may not be the same -- `vmov q3[3],q3[1],r3,r3' The code generated for f here is: f: movs r2, #0 movs r3, #0 vmov q3[2], q3[0], r2, r2 vmov q3[3], q3[1], r3, r3 ldr r3, .L2 vstrw.32 q3, [r3] bx lr The problem also occurs for other types when used with vcreateq, e.g. for: #include <arm_mve.h> uint32x4_t v; void f(void) { v = vcreateq_u32(0, 0); } Here is a preprocessed testcase (not for the testsuite, but for testing with a cc1): __simd128_uint64_t v; void f(void) { v = __builtin_mve_vcreateq_uv2di(0, 0); }
next reply other threads:[~2021-05-12 19:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-12 19:51 acoplan at gcc dot gnu.org [this message] 2021-05-12 19:52 ` [Bug target/100572] " acoplan at gcc dot gnu.org 2021-05-13 9:16 ` acoplan at gcc dot gnu.org 2021-05-13 10:03 ` 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-100572-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).