From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: Add __builtin_bit_cast to implement std::bit_cast [PR93121]
Date: Fri, 31 Jul 2020 12:06:25 +0200 [thread overview]
Message-ID: <20200731100625.GF2363@tucnak> (raw)
In-Reply-To: <20200731095446.GU3400@redhat.com>
On Fri, Jul 31, 2020 at 10:54:46AM +0100, Jonathan Wakely wrote:
> > Does the standard require that somewhere? Because that is not what the
> > compiler implements right now.
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78620
Ah, ok.
But does that imply that all CONSTRUCTORs without CONSTRUCTOR_NO_CLEARING
need to be treated that way? I mean, aren't such CONSTRUCTORs used also for
other initializations?
And, are the default copy constructors or assignment operators supposed to
also copy the padding bits, or do they become unspecified again through
that?
Jakub
next prev parent reply other threads:[~2020-07-31 10:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 18:50 Jakub Jelinek
2020-07-22 14:03 ` Paul Koning
2020-07-30 14:16 ` Jason Merrill
2020-07-30 14:57 ` Jakub Jelinek
2020-07-30 21:59 ` Jason Merrill
2020-07-31 8:19 ` Jakub Jelinek
2020-07-31 9:54 ` Jonathan Wakely
2020-07-31 10:06 ` Jakub Jelinek [this message]
2020-07-31 20:28 ` Jason Merrill
2020-08-27 10:06 ` Jakub Jelinek
2020-08-27 10:19 ` Richard Biener
2020-09-02 21:52 ` Jason Merrill
2020-08-27 10:46 ` Jakub Jelinek
2020-08-27 11:06 ` Jonathan Wakely
2020-08-27 11:17 ` Jakub Jelinek
2020-08-27 11:22 ` Jonathan Wakely
2020-08-27 10:59 ` Jonathan Wakely
2020-08-27 20:43 ` Iain Buclaw
2020-11-02 19:21 ` [PATCH] c++: v2: " Jakub Jelinek
2020-11-25 0:31 ` Jeff Law
2020-11-25 9:23 ` Jakub Jelinek
2020-11-25 10:31 ` Jonathan Wakely
2020-11-25 16:24 ` Jakub Jelinek
2020-11-25 16:28 ` Jonathan Wakely
2020-11-25 17:26 ` Jason Merrill
2020-11-25 18:50 ` Jakub Jelinek
2020-11-26 0:52 ` Jason Merrill
2020-11-26 15:09 ` [PATCH] c++: v3: " Jakub Jelinek
2020-12-03 14:24 ` Jason Merrill
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=20200731100625.GF2363@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely@redhat.com \
/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).