public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38698] [4.4 regression] ICE initializing union with initializer list
Date: Sat, 03 Jan 2009 00:22:00 -0000	[thread overview]
Message-ID: <20090103002119.20010.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38698-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jason at gcc dot gnu dot org  2009-01-03 00:21 -------
Subject: Bug 38698

Author: jason
Date: Sat Jan  3 00:19:55 2009
New Revision: 143024

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143024
Log:
        PR c++/38698
        * typeck2.c (process_init_constructor_union): Handle excess
        initializers.
        (process_init_constructor_record): Likewise.

        PR c++/38684
        * typeck2.c (digest_init_r): Don't use process_init_constructor
        for non-aggregate classes.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/initlist11.C
    trunk/gcc/testsuite/g++.dg/cpp0x/initlist12.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/typeck2.c
    trunk/gcc/testsuite/ChangeLog


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38698


  parent reply	other threads:[~2009-01-03  0:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 14:34 [Bug c++/38698] New: " reichelt at gcc dot gnu dot org
2009-01-02 14:35 ` [Bug c++/38698] " reichelt at gcc dot gnu dot org
2009-01-02 15:37 ` paolo dot carlini at oracle dot com
2009-01-02 16:35 ` jason at gcc dot gnu dot org
2009-01-03  0:22 ` jason at gcc dot gnu dot org [this message]
2009-01-03  1:04 ` jakub at gcc dot gnu dot org
2009-01-04 21:37 ` reichelt at gcc dot gnu dot org
2009-01-05 11:31 ` rguenth at gcc dot gnu dot org
2009-01-06  3:27 ` jason at gcc dot gnu dot org
2009-01-06 13:50 ` jakub at gcc dot gnu dot 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=20090103002119.20010.qmail@sourceware.org \
    --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).