public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109495] Stack is used (unexpectedly) for copying on-heap objects (no problem in clang)
Date: Thu, 13 Apr 2023 13:00:24 +0000 [thread overview]
Message-ID: <bug-109495-4-Zadc8r73CD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109495-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109495
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The private keyword makes it non-POD and so the tail padding can be reused and
we need to make sure we copy only the bits except for type padding.
I guess we need some archeology why the exact conditions are in there.
next prev parent reply other threads:[~2023-04-13 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 11:08 [Bug c++/109495] New: Stack is used (unexpectedly) for copying on-heap objects (while clang doesn't) gcc-bug-reports at xhtml dot guru
2023-04-13 11:10 ` [Bug c++/109495] Stack is used (unexpectedly) for copying on-heap objects (no problem in clang) gcc-bug-reports at xhtml dot guru
2023-04-13 11:49 ` [Bug middle-end/109495] " rguenth at gcc dot gnu.org
2023-04-13 12:16 ` jakub at gcc dot gnu.org
2023-04-13 12:45 ` rguenth at gcc dot gnu.org
2023-04-13 12:59 ` rguenth at gcc dot gnu.org
2023-04-13 13:00 ` jakub at gcc dot gnu.org [this message]
2023-04-14 8:12 ` rguenth 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-109495-4-Zadc8r73CD@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).