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++/25633] [3.4/4.0/4.1/4.2 regression] ICE on invalid initializer in constructor
Date: Tue, 03 Jan 2006 08:41:00 -0000	[thread overview]
Message-ID: <20060103084130.22466.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25633-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from mmitchel at gcc dot gnu dot org  2006-01-03 08:41 -------
Subject: Bug 25633

Author: mmitchel
Date: Tue Jan  3 08:41:21 2006
New Revision: 109270

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109270
Log:
        PR c++/25635
        * class.c (add_method): Set TYPE_HAS_CONVERSION for classes with a
        conversion operator.
        * decl.c (grokdeclarator): Do not set TYPE_HAS_CONVERSION here.
        PR c++/25638
        * class.c (add_method): Never associate more than one destructor
        with a single class.
        PR c++/25637
        * cp-tree.h (do_friend): Adjust prototype.
        * decl.c (grokfndecl): Make funcdef_flag a bool, not an int.
        (grokdeclarator): Likewise.  Refine check for invalid
        declarations/definitions of member functions outside of their own
        class.
        * friend.c (do_friend): Make funcdef_flag a bool, not an int.
        PR c++/25633
        * parser.c (cp_parser_mem_initializer_list): Check result of
        cp_parser_mem_initializer against error_mark_node, not NULL_TREE.
        (cp_parser_mem_initializer): Return error_mark_node for failure.
        PR c++/25634
        * parser.c (cp_parser_template_parameter_list): Call
        begin_template_parm_list and end_template_parm_list here.
        (cp_parser_type_parameter): Not here.
        (cp_parser_template_declaration_after_export): Or here.
        (cp_parser_elaborated_type_specifier): Call
        cp_parser_check_template_parameters.
        * tree.c (build_target_expr_with_type): Use force_target_expr.
        PR c++/25635
        * g++.dg/parse/operator6.C: New test.
        PR c++/25637
        * g++.dg/parse/error29.C: New test.
        PR c++/25638
        * g++.dg/parse/dtor6.C: New test.
        PR c++/25633
        * g++.dg/parse/ctor3.C: New test.
        PR c++/25634
        * g++.dg/template/class3.C: New test.

Added:
    trunk/gcc/testsuite/g++.dg/parse/ctor3.C
    trunk/gcc/testsuite/g++.dg/parse/dtor6.C
    trunk/gcc/testsuite/g++.dg/parse/error29.C
    trunk/gcc/testsuite/g++.dg/parse/operator6.C
    trunk/gcc/testsuite/g++.dg/template/class3.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/class.c
    trunk/gcc/cp/cp-tree.h
    trunk/gcc/cp/decl.c
    trunk/gcc/cp/friend.c
    trunk/gcc/cp/parser.c
    trunk/gcc/cp/tree.c
    trunk/gcc/testsuite/ChangeLog


-- 


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



  parent reply	other threads:[~2006-01-03  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02 12:19 [Bug c++/25633] New: " reichelt at gcc dot gnu dot org
2006-01-02 16:46 ` [Bug c++/25633] " pinskia at gcc dot gnu dot org
2006-01-03  0:51 ` mmitchel at gcc dot gnu dot org
2006-01-03  8:38 ` mmitchel at gcc dot gnu dot org
2006-01-03  8:40 ` mmitchel at gcc dot gnu dot org
2006-01-03  8:41 ` mmitchel at gcc dot gnu dot org [this message]
2006-01-03  8:50 ` [Bug c++/25633] [3.4 " mmitchel at gcc dot gnu dot org
2006-03-01  5:08 ` gdr 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=20060103084130.22466.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).