public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105923] unsupported return type ‘complex double’ for simd
Date: Wed, 15 Jun 2022 18:41:40 +0000 [thread overview]
Message-ID: <bug-105923-4-0bP2SrOr0R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105923-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105923
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Hongtao.liu from comment #6)
> > .L3:
> > subl %r13d, %r12d
> > cmpl $1, %r12d
> > je .L6
> > salq $4, %r13
> > vmovapd a(%r13), %xmm0
> > call _ZGVbN2v_foo
> > vmovapd %xmm0, b(%r13)
>
> hmm, xmm version should be abandoned since it's just 1 complex double.
If there is an XMM version of a vector complex, will it be faster than
passing complex double as a struct in 2 registers.
next prev parent reply other threads:[~2022-06-15 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 1:32 [Bug target/105923] New: " hjl.tools at gmail dot com
2022-06-11 1:35 ` [Bug c/105923] " pinskia at gcc dot gnu.org
2022-06-14 7:39 ` rguenth at gcc dot gnu.org
2022-06-14 7:52 ` crazylht at gmail dot com
2022-06-14 9:10 ` crazylht at gmail dot com
2022-06-15 8:10 ` crazylht at gmail dot com
2022-06-15 8:12 ` crazylht at gmail dot com
2022-06-15 18:41 ` hjl.tools at gmail dot com [this message]
2022-07-20 8:15 ` crazylht at gmail dot 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-105923-4-0bP2SrOr0R@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).