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++/96592] [10 Regression] Tuple element w/ member reference to incomplete template type rejected
Date: Mon, 29 Mar 2021 20:04:34 +0000	[thread overview]
Message-ID: <bug-96592-4-xZOGZ7cKtf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96592-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:202e96058031b8ac2edc8fdab2faab06b988a253

commit r10-9607-g202e96058031b8ac2edc8fdab2faab06b988a253
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Sep 3 16:26:16 2020 +0100

    libstdc++: Add workaround for weird std::tuple error [PR 96592]

    This "fix" makes no sense, but it avoids an error from G++ about
    std::is_constructible being incomplete. The real problem is elsewhere,
    but this "fixes" the regression for now.

    libstdc++-v3/ChangeLog:

            PR libstdc++/96592
            * include/std/tuple (_TupleConstraints<true, T...>): Use
            alternative is_constructible instead of std::is_constructible.
            * testsuite/20_util/tuple/cons/96592.cc: New test.

    (cherry picked from commit 032a4b42cc5f2105f622690ce2552f1c30e1d227)

  parent reply	other threads:[~2021-03-29 20:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 16:15 [Bug c++/96592] New: " cuzdav at gmail dot com
2020-08-14  0:19 ` [Bug c++/96592] " johnilacqua at hotmail dot com
2020-08-17 21:51 ` [Bug libstdc++/96592] [10/11 Regression] " mpolacek at gcc dot gnu.org
2020-09-03 15:18 ` redi at gcc dot gnu.org
2020-09-03 15:37 ` cvs-commit at gcc dot gnu.org
2020-09-03 15:38 ` [Bug libstdc++/96592] [10 " redi at gcc dot gnu.org
2020-09-03 15:43 ` redi at gcc dot gnu.org
2020-12-17 15:12 ` ppalka at gcc dot gnu.org
2021-03-29 20:04 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-30  4:18 ` ppalka at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-11-26 17:41 ` redi at gcc dot gnu.org
2021-11-26 17:41 ` redi at gcc dot gnu.org
2021-11-26 23:07 ` cvs-commit at gcc dot gnu.org
2022-04-21 15:34 ` 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-96592-4-xZOGZ7cKtf@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).