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 libstdc++/100667] [11/12/13 Regression] std::tuple<A&&> cannot be constructed from A&&, if A not defined (only forward declared)
Date: Wed, 01 May 2024 20:31:44 +0000	[thread overview]
Message-ID: <bug-100667-4-ESFmChHZiA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100667-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:19821ce86afa0f4ce0d2312b16864c809e605be9

commit r13-8667-g19821ce86afa0f4ce0d2312b16864c809e605be9
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Mar 27 16:14:01 2024 -0400

    c++: __is_constructible ref binding [PR100667]

    The requirement that a type argument be complete is excessive in the case
of
    direct reference binding to the same type, which does not rely on any
    properties of the type.  This is LWG 2939.

            PR c++/100667

    gcc/cp/ChangeLog:

            * semantics.cc (same_type_ref_bind_p): New.
            (finish_trait_expr): Use it.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/is_constructible8.C: New test.

    (cherry picked from commit 8bb3ef3f6e335e8794590fb712a2661d11d21973)

  parent reply	other threads:[~2024-05-01 20:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:00 [Bug libstdc++/100667] New: " piotrwn1 at gmail dot com
2021-05-19  9:09 ` [Bug libstdc++/100667] [11/12 Regression] " redi at gcc dot gnu.org
2021-06-18  7:56 ` ostash at ostash dot kiev.ua
2021-07-28  7:07 ` rguenth at gcc dot gnu.org
2022-04-21  7:49 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` [Bug libstdc++/100667] [11/12/13/14 " jakub at gcc dot gnu.org
2023-05-29 11:16 ` piotrwn1 at gmail dot com
2024-03-27 12:59 ` redi at gcc dot gnu.org
2024-03-27 13:36 ` redi at gcc dot gnu.org
2024-03-27 14:02 ` redi at gcc dot gnu.org
2024-03-27 14:03 ` redi at gcc dot gnu.org
2024-03-27 14:14 ` redi at gcc dot gnu.org
2024-03-27 17:44 ` redi at gcc dot gnu.org
2024-03-28 18:26 ` cvs-commit at gcc dot gnu.org
2024-03-28 22:33 ` [Bug libstdc++/100667] [11/12/13 " redi at gcc dot gnu.org
2024-05-01 20:31 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-24 15:59 ` [Bug libstdc++/100667] [11/12 " cvs-commit at gcc dot gnu.org
2024-05-24 18:38 ` cvs-commit 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-100667-4-ESFmChHZiA@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).