public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98884] Implement empty struct optimisations on ARM
Date: Fri, 29 Jan 2021 11:43:00 +0000	[thread overview]
Message-ID: <bug-98884-4-X8INnK8SaO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98884-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c++                         |target
             Target|                            |arm

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
IIRC x86_64 had to change how empty structs are passed, to make C++ consistent
with the x86_64 psABI as used by C (and it wasn't a trivial change to get
right).

If the ARM ABI requires stack space for them then that's unavoidable, but
they're just padding bytes so leaving that stack space uninitialized should be
OK.

Reassigning to the arm target.

  reply	other threads:[~2021-01-29 11:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 11:18 [Bug c++/98884] New: " david at westcontrol dot com
2021-01-29 11:43 ` redi at gcc dot gnu.org [this message]
2021-01-29 11:55 ` [Bug target/98884] " rguenth at gcc dot gnu.org
2021-01-29 12:30 ` david at westcontrol dot com
2021-01-29 12:35 ` jakub at gcc dot gnu.org
2021-01-29 12:48 ` jakub at gcc dot gnu.org
2021-02-01 15:18 ` david at westcontrol dot com
2021-02-01 15:46 ` david at westcontrol dot com
2021-02-01 16:34 ` jakub 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-98884-4-X8INnK8SaO@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).