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++/96803] std::tuple chooses wrong constructor for uses-allocator construction
Date: Tue, 22 Sep 2020 07:42:46 +0000	[thread overview]
Message-ID: <bug-96803-4-42N99Fz495@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96803-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:7825399092d572ce8ea82c4aa8dfeb65076b0e52

commit r11-3348-g7825399092d572ce8ea82c4aa8dfeb65076b0e52
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Sep 22 08:42:18 2020 +0100

    libstdc++: Use correct argument type for __use_alloc, again [PR 96803]

    While backporting 5494edae83ad33c769bd1ebc98f0c492453a6417 I noticed
    that it's still not correct. I made the allocator-extended constructor
    use the right type for the uses-allocator construction detection, but I
    used an rvalue when it should be a const lvalue.

    This should fix it properly this time.

    libstdc++-v3/ChangeLog:

            PR libstdc++/96803
            * include/std/tuple
            (_Tuple_impl(allocator_arg_t, Alloc, const _Tuple_impl<U...>&)):
            Use correct value category in __use_alloc call.
            * testsuite/20_util/tuple/cons/96803.cc: Check with constructors
            that require correct value category to be used.

  parent reply	other threads:[~2020-09-22  7:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 17:16 [Bug libstdc++/96803] New: " redi at gcc dot gnu.org
2020-08-26 17:16 ` [Bug libstdc++/96803] " redi at gcc dot gnu.org
2020-08-26 18:30 ` redi at gcc dot gnu.org
2020-08-26 18:33 ` cvs-commit at gcc dot gnu.org
2020-09-22  6:47 ` cvs-commit at gcc dot gnu.org
2020-09-22  6:48 ` cvs-commit at gcc dot gnu.org
2020-09-22  7:42 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-22  9:40 ` cvs-commit at gcc dot gnu.org
2020-09-22  9:40 ` cvs-commit at gcc dot gnu.org
2020-09-22  9:41 ` cvs-commit at gcc dot gnu.org
2020-09-22  9:41 ` 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-96803-4-42N99Fz495@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).