public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/61947] [4.8/4.9/4.10 Regression] Ambiguous calls when constructing std::tuple
Date: Tue, 29 Jul 2014 17:31:00 -0000	[thread overview]
Message-ID: <bug-61947-4-VaVfsMpfJg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61947-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jul 29 17:30:34 2014
New Revision: 213221

URL: https://gcc.gnu.org/viewcvs?rev=213221&root=gcc&view=rev
Log:
    PR libstdc++/61947
    * include/std/tuple (_Head_base): Use allocator_arg_t parameters to
    disambiguate unary constructors.
    (_Tuple_impl): Pass allocator_arg_t arguments.
    * testsuite/20_util/tuple/61947.cc: New.
    * testsuite/20_util/uses_allocator/cons_neg.cc: Adjust dg-error line.

Added:
    trunk/libstdc++-v3/testsuite/20_util/tuple/61947.cc
      - copied, changed from r213220,
trunk/libstdc++-v3/testsuite/20_util/uses_allocator/cons_neg.cc
Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/include/std/tuple
    trunk/libstdc++-v3/testsuite/20_util/uses_allocator/cons_neg.cc


  parent reply	other threads:[~2014-07-29 17:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 11:07 [Bug libstdc++/61947] New: " roman.perepelitsa at gmail dot com
2014-07-29 11:35 ` [Bug libstdc++/61947] [4.8/4.9/4.10 Regression] " redi at gcc dot gnu.org
2014-07-29 11:54 ` redi at gcc dot gnu.org
2014-07-29 15:17 ` ppluzhnikov at google dot com
2014-07-29 17:31 ` redi at gcc dot gnu.org [this message]
2014-07-29 17:34 ` redi at gcc dot gnu.org
2014-11-19 13:30 ` [Bug libstdc++/61947] [4.8/4.9 " rguenth at gcc dot gnu.org
2014-12-06 20:38 ` redi at gcc dot gnu.org
2014-12-06 22:24 ` redi at gcc dot gnu.org
2014-12-06 22:29 ` 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-61947-4-VaVfsMpfJg@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).