public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/115480] Difference between trivial copyability of std::pair under Clang in C++23
Date: Thu, 13 Jun 2024 18:30:17 +0000 [thread overview]
Message-ID: <bug-115480-4-e9bxVJO8kV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115480-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115480
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Note the change for GCC 12.3.0 that fix it was r12-8799-gaeba3e009b0abf .
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602548.html
next prev parent reply other threads:[~2024-06-13 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 18:09 [Bug libstdc++/115480] New: " ldionne.2 at gmail dot com
2024-06-13 18:15 ` [Bug c++/115480] " pinskia at gcc dot gnu.org
2024-06-13 18:20 ` pinskia at gcc dot gnu.org
2024-06-13 18:24 ` pinskia at gcc dot gnu.org
2024-06-13 18:28 ` pinskia at gcc dot gnu.org
2024-06-13 18:30 ` pinskia at gcc dot gnu.org [this message]
2024-06-14 15:35 ` redi 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-115480-4-e9bxVJO8kV@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).