public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/32245] [4.1/4.2 Regression] wrong POD type initialization with pointer to member
Date: Sat, 07 Jul 2007 02:03:00 -0000	[thread overview]
Message-ID: <20070707020256.29064.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32245-10812@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from mmitchel at gcc dot gnu dot org  2007-07-07 02:02 -------
Subject: Bug 32245

Author: mmitchel
Date: Sat Jul  7 02:02:37 2007
New Revision: 126433

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126433
Log:
        PR c++/32245
        * init.c (build_zero_init): Always build an initializer for
        non-static storage.
        * typeck2.c (build_functional_cast): Use build_zero_init.

        PR c++/32251
        * init.c (build_new_1): Always pass the allocation function to
        build_op_delete_call.
        * call.c (build_op_delete_call): Handle operator delete with a
        variable-argument list.  Do not issue an error when no matching
        deallocation function is available for a new operator.

        PR c++/31992
        * cp-tree.h (any_value_dependent_elements_p): Declare it.
        * decl.c (value_dependent_init_p): New function.
        (cp_finish_decl): Use it.
        * pt.c (value_dependent_expression_p): Use
        any_value_dependent_elements_p.
        * parser.c (cp_parser_primary_expression): Add comment about
        treating dependent qualified names as integral
        constant-expressions.

        PR c++/32245
        * g++.dg/init/ptrmem4.C: New test.

        PR c++/32251
        * g++.dg/init/new21.C: Likewise.

        PR c++/31992
        * g++.dg/template/static30.C: Likewise.

Added:
    branches/gcc-4_2-branch/gcc/testsuite/g++.dg/init/new21.C
    branches/gcc-4_2-branch/gcc/testsuite/g++.dg/init/ptrmem4.C
    branches/gcc-4_2-branch/gcc/testsuite/g++.dg/template/static30.C
Modified:
    branches/gcc-4_2-branch/gcc/cp/ChangeLog
    branches/gcc-4_2-branch/gcc/cp/call.c
    branches/gcc-4_2-branch/gcc/cp/cp-tree.h
    branches/gcc-4_2-branch/gcc/cp/decl.c
    branches/gcc-4_2-branch/gcc/cp/init.c
    branches/gcc-4_2-branch/gcc/cp/parser.c
    branches/gcc-4_2-branch/gcc/cp/pt.c
    branches/gcc-4_2-branch/gcc/cp/typeck2.c
    branches/gcc-4_2-branch/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2007-07-07  2:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 13:37 [Bug c++/32245] New: wrong POD type initialization s__nakayama at infoseek dot jp
2007-06-08 10:37 ` [Bug c++/32245] [4.1/4.2/4.3 Regression] wrong POD type initialization with pointer to member rguenth at gcc dot gnu dot org
2007-06-30  9:15 ` pinskia at gcc dot gnu dot org
2007-07-04  3:24 ` mmitchel at gcc dot gnu dot org
2007-07-04 19:02 ` mmitchel at gcc dot gnu dot org
2007-07-06  1:24 ` mmitchel at gcc dot gnu dot org
2007-07-06  1:37 ` [Bug c++/32245] [4.1/4.2 " mmitchel at gcc dot gnu dot org
2007-07-07  2:03 ` mmitchel at gcc dot gnu dot org [this message]
2007-07-07  2:05 ` [Bug c++/32245] [4.1 " mmitchel at gcc dot gnu dot org
2007-11-30 10:43 ` aaw at gcc dot gnu dot org
2007-11-30 10:49 ` rguenth at gcc dot gnu dot org
2008-07-04 16:08 ` jsm28 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=20070707020256.29064.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).