public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mhillen at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101876] [s390x] vector builtin vec_permi fails to resolve with #pragma GCC target Date: Wed, 18 Aug 2021 14:07:49 +0000 [thread overview] Message-ID: <bug-101876-4-mcXXLaGO17@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101876-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101876 --- Comment #2 from Marius Hillenbrand <mhillen at linux dot ibm.com> --- Narrowed down what triggers the issue after experimenting with another example: when the pragma sets 'vx' before the typedef, then the resulting type definition appears broken. when enabling 'vx' only after the typedef, then the example compiles successfully. updated example: #ifdef BROKEN #pragma GCC target("arch=z13") // note: z13 implies vx #else #pragma GCC target("arch=z13,no-vx") // ... so turn off 'vx' again #endif #include <vecintrin.h> typedef unsigned long long v2di __attribute__((vector_size(16))); #ifndef BROKEN #pragma GCC target("vx") #endif v2di foo(char *ptr) { v2di v = *(v2di *)ptr; v = vec_permi(v, v, 0); return v; } Compile fails gcc -march=z10 -O3 -DBROKEN -c -S -o- example.c but succeeds without -DBROKEN
next prev parent reply other threads:[~2021-08-18 14:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-12 10:28 [Bug middle-end/101876] New: [290x] " mhillen at linux dot ibm.com 2021-08-12 10:30 ` [Bug middle-end/101876] " mhillen at linux dot ibm.com 2021-08-18 14:07 ` mhillen at linux dot ibm.com [this message] 2021-08-20 15:21 ` [Bug target/101876] [s390x] " mhillen at linux dot ibm.com 2021-08-20 15:22 ` mhillen at linux dot ibm.com 2021-09-27 12:25 ` mhillen at linux dot ibm.com
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-101876-4-mcXXLaGO17@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).