public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102535] __is_trivially_constructible rejects some trivial cases in aggregate initializations
Date: Tue, 12 Oct 2021 11:00:10 +0000	[thread overview]
Message-ID: <bug-102535-4-SHhNYh4FtG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102535-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:7b4e6d75b18dbb52bf507dbfd4c8e694e476d2af

commit r11-9120-g7b4e6d75b18dbb52bf507dbfd4c8e694e476d2af
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Oct 5 09:32:11 2021 +0100

    libstdc++: Fix testcase for newly-implemented C++20 semantics [PR102535]

    libstdc++-v3/ChangeLog:

            PR c++/102535
            * testsuite/20_util/is_trivially_constructible/value.cc: Adjust
            expected value for C++20.

    (cherry picked from commit 7646847df71e57edca5ec5b8c3c3dc4550dcb49d)

  parent reply	other threads:[~2021-10-12 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  2:45 [Bug c++/102535] New: " de34 at live dot cn
2021-09-30 14:59 ` [Bug c++/102535] " ppalka at gcc dot gnu.org
2021-09-30 21:51 ` cvs-commit at gcc dot gnu.org
2021-10-05  8:36 ` cvs-commit at gcc dot gnu.org
2021-10-06 14:15 ` cvs-commit at gcc dot gnu.org
2021-10-12 11:00 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-12 13:33 ` ppalka 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-102535-4-SHhNYh4FtG@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).