public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lee.imple at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/114417] std::experimental::simd is not a POD (by ABI definitions) and is always passed by reference instead of by value
Date: Mon, 22 Apr 2024 17:18:18 +0000	[thread overview]
Message-ID: <bug-114417-4-BL7ZJWBXdN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114417-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Imple Lee <lee.imple at gmail dot com> ---
> What you want to use instead is std::experimental::simd_abi::deduce_t<T, N>. That'll give you a not-fixed_size ABI if one exists. And those will likely be passed via registers (as long as the psABI allows).

Great! It does work as intended. Thank you for telling me that.
Maybe all I need is just to read the docs on cppref more carefully :|

      parent reply	other threads:[~2024-04-22 17:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 16:05 [Bug libstdc++/114417] New: simd parameters are passed by memory on x64 , not using the available sse registers lee.imple at gmail dot com
2024-03-21 16:09 ` [Bug target/114417] " pinskia at gcc dot gnu.org
2024-03-21 16:16 ` lee.imple at gmail dot com
2024-03-21 16:17 ` lee.imple at gmail dot com
2024-03-21 16:26 ` [Bug target/114417] std::experimental::simd " pinskia at gcc dot gnu.org
2024-03-21 16:28 ` pinskia at gcc dot gnu.org
2024-03-21 16:34 ` [Bug libstdc++/114417] std::experimental::simd is not a POD (by ABI definitions) and is always passed by reference instead of by value pinskia at gcc dot gnu.org
2024-03-21 16:37 ` pinskia at gcc dot gnu.org
2024-03-21 18:01 ` lee.imple at gmail dot com
2024-03-22  1:37 ` de34 at live dot cn
2024-04-22 12:46 ` mkretz at gcc dot gnu.org
2024-04-22 12:48 ` mkretz at gcc dot gnu.org
2024-04-22 17:18 ` lee.imple at gmail dot com [this message]

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-114417-4-BL7ZJWBXdN@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).