public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96895] ABI of returning V1DF differs between GCC and clang Date: Wed, 02 Sep 2020 08:29:44 +0000 [thread overview] Message-ID: <bug-96895-4-Wajk2iTp1n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96895-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96895 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-*-* Keywords| |ABI CC| |hjl at gcc dot gnu.org, | |matz at gcc dot gnu.org --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- I guess the psABI does not say anything about "non-standard" vector types. Note v1sf seems to be returned in %xmm0 with GCC but %eax with clang which passes v1sf in general regs as well while GCC passes in %xmm0. typedef float v1df __attribute__((vector_size(4))); v1df foo (v1df x) { return x; }
next prev parent reply other threads:[~2020-09-02 8:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-02 8:24 [Bug target/96895] New: " rguenth at gcc dot gnu.org 2020-09-02 8:29 ` rguenth at gcc dot gnu.org [this message] 2020-09-02 12:14 ` [Bug target/96895] " matz at gcc dot gnu.org 2020-09-02 12:15 ` hjl.tools at gmail dot com 2020-09-02 12:18 ` hjl.tools at gmail dot com 2020-09-02 14:08 ` rguenth at gcc dot gnu.org 2020-09-02 14:16 ` rguenth at gcc dot gnu.org 2020-09-02 14:28 ` matz at gcc dot gnu.org 2023-12-04 10:18 ` egallager 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-96895-4-Wajk2iTp1n@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).