public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51747] [DR 1467] [C++11] cannot call defaulted copy constructor using list-initialization
Date: Thu, 07 May 2015 16:47:00 -0000	[thread overview]
Message-ID: <bug-51747-4-hCwzVvJDCa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51747-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Thu May  7 16:46:58 2015
New Revision: 222882

URL: https://gcc.gnu.org/viewcvs?rev=222882&root=gcc&view=rev
Log:
        DR 1467
        PR c++/51747
        * typeck2.c (digest_init_r): Fix single element list.

Added:
    branches/gcc-5-branch/gcc/testsuite/g++.dg/cpp0x/initlist95.C
Modified:
    branches/gcc-5-branch/gcc/cp/ChangeLog
    branches/gcc-5-branch/gcc/cp/typeck2.c


  parent reply	other threads:[~2015-05-07 16:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 22:04 [Bug c++/51747] New: [C++11] cannot call " redi at gcc dot gnu.org
2012-02-02  6:08 ` [Bug c++/51747] [C++11] cannot call defaulted " pinskia at gcc dot gnu.org
2013-04-25 11:30 ` redi at gcc dot gnu.org
2014-03-19 17:29 ` [Bug c++/51747] [DR 1467] " redi at gcc dot gnu.org
2014-03-19 17:31 ` redi at gcc dot gnu.org
2014-03-20 21:27 ` jason at gcc dot gnu.org
2014-03-24 16:03 ` jason at gcc dot gnu.org
2014-04-11 18:25 ` jason at gcc dot gnu.org
2014-05-05 16:05 ` jason at gcc dot gnu.org
2015-01-16  9:10 ` ville.voutilainen at gmail dot com
2015-01-16 17:04 ` tom at honermann dot net
2015-01-25 18:35 ` ville.voutilainen at gmail dot com
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-05-07 16:47 ` jason at gcc dot gnu.org [this message]
2015-05-07 16:47 ` jason at gcc dot gnu.org
2015-05-07 16:48 ` jason at gcc dot gnu.org
2015-06-09 16:56 ` jason 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-51747-4-hCwzVvJDCa@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).