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: Fri, 20 Aug 2021 15:21:34 +0000 [thread overview] Message-ID: <bug-101876-4-Y4V3MqtU66@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 #3 from Marius Hillenbrand <mhillen at linux dot ibm.com> --- The issue is caused by inconsistent alignment of vector_types between the types (a) expected or returned by builtin functions and (b) the typedef in the example code. In the failing cases, there's a mismatch of 16-Byte and 8-Byte (compliant with the ABI) alignment. In the successful cases, either both use 16-Byte or 8-Byte alignment. When gcc starts, s390_init_builtins defines builtin functions with their corresponding type information. That includes vector builtins. While creating the builtin types for these builtins, when gcc starts with -march < z13, then s390_vector_alignment defers to default_vector_alignment, which results in natural alignment. That results in 16-Byte alignment of the 16-Byte vectors. Once the pragma switched to an arch level with VX support (TARGET_VX and TARGET_VX_ABI are true), then s390_vector_alignment selects 8-Byte alignment in accordance with the vector ABI. The C++ example (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101877) ICEs because two structurally identical vector types have different canonical types (as a result of the different alignment?!).
next prev parent reply other threads:[~2021-08-20 15:21 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 ` [Bug target/101876] [s390x] " mhillen at linux dot ibm.com 2021-08-20 15:21 ` mhillen at linux dot ibm.com [this message] 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-Y4V3MqtU66@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).