public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nikolasklauser at berlin dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107187] New: [feature request] Add `trivial_abi` attribute
Date: Sat, 08 Oct 2022 22:28:26 +0000	[thread overview]
Message-ID: <bug-107187-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107187
           Summary: [feature request] Add `trivial_abi` attribute
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nikolasklauser at berlin dot de
  Target Milestone: ---

This attribute is implemented by clang. It changes the calling convention of
non-trivial class types to be trivial for the purpose of calls (with some
caveats). libc++ has used it in the unstable ABI for some time now, and we'd
like to use it for new types in the stable ABI too, since it can improve
performance dramatically. I'm sure libstdc++ (and other libraries) will find it
useful too.

See https://quuxplusone.github.io/blog/2018/05/02/trivial-abi-101/ for a more
detailed explanation of it's benefits and drawbacks and
https://clang.llvm.org/docs/AttributeReference.html#trivial-abi for the clang
documentation.

             reply	other threads:[~2022-10-08 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 22:28 nikolasklauser at berlin dot de [this message]
2022-10-08 22:34 ` [Bug c++/107187] " pinskia at gcc dot gnu.org
2022-10-08 22:37 ` pinskia 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-107187-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).