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] New: ABI of returning V1DF differs between GCC and clang
Date: Wed, 02 Sep 2020 08:24:59 +0000	[thread overview]
Message-ID: <bug-96895-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96895

            Bug ID: 96895
           Summary: ABI of returning V1DF differs between GCC and clang
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

clang and GCC differ in returning v1df:

typedef double v1df __attribute__((vector_size(8)));
v1df foo (v1df x)
{
  return x;
}

clang returns in %xmm0 while GCC returns by invisible reference (thus in
memory).
v1df arguments are passed on the stack with both compilers.

GCC behaves this way because the v1df type has BLKmode.  If we assign
the type DFmode (V1DFmode is unavailable) then GCC passes and returns in %xmm0.
The target should likely not work on modes here but on types.

             reply	other threads:[~2020-09-02  8:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  8:24 rguenth at gcc dot gnu.org [this message]
2020-09-02  8:29 ` [Bug target/96895] " rguenth at gcc dot gnu.org
2020-09-02 12:14 ` 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@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: link
Be 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).