public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/30818] [4.1/4.2/4.3 Regression] templates and typedefs cause function prototype not to match Date: Sun, 22 Jul 2007 16:26:00 -0000 [thread overview] Message-ID: <20070722162605.608.qmail@sourceware.org> (raw) In-Reply-To: <bug-30818-5268@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from nathan at gcc dot gnu dot org 2007-07-22 16:26 ------- Subject: Bug 30818 Author: nathan Date: Sun Jul 22 16:25:54 2007 New Revision: 126825 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126825 Log: cp/ PR c++/30818 * typeck.c (structural_comptypes): No need to check resolve_typename_type return value here. * cp-tree.h (TYPENAME_IS_RESOLVING_P): New. * pt.c (resolve_typename_type): Follow typename typedefs. Return original type rather than error_mark_node in case of failure. * parser.c (cp_parser_nested_name_specifier_opt): Adjust resolve_typename_type result check. (cp_parser_direct_declarator, cp_parser_head, cp_parser_constructor_declarator_p): Likewise. testsuite/ PR c++/30818 * g++.dg/template/crash47.C: Adjust errors. * g++.dg/template/crash48.C: Adjust errors. * g++.dg/template/typename12.C: New. * g++.dg/template/typename13.C: New. * g++.dg/template/typename14.C: New. * g++.dg/template/typedef6.C: Adjust errors. Added: trunk/gcc/testsuite/g++.dg/template/typename12.C trunk/gcc/testsuite/g++.dg/template/typename13.C trunk/gcc/testsuite/g++.dg/template/typename14.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/cp-tree.h trunk/gcc/cp/parser.c trunk/gcc/cp/pt.c trunk/gcc/cp/typeck.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/template/crash47.C trunk/gcc/testsuite/g++.dg/template/crash48.C trunk/gcc/testsuite/g++.dg/template/typedef6.C -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30818
next prev parent reply other threads:[~2007-07-22 16:26 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-16 10:30 [Bug c++/30818] New: [4.1.2 " sschunck at pdf dot de 2007-02-16 11:25 ` [Bug c++/30818] [4.1/4.2/4.3 " rguenth at gcc dot gnu dot org 2007-02-16 13:47 ` rguenth at gcc dot gnu dot org 2007-02-21 15:23 ` rguenth at gcc dot gnu dot org 2007-03-05 3:58 ` mmitchel at gcc dot gnu dot org 2007-04-23 21:26 ` janis at gcc dot gnu dot org 2007-04-23 21:29 ` pinskia at gcc dot gnu dot org 2007-07-21 20:51 ` nathan at gcc dot gnu dot org 2007-07-22 16:26 ` nathan at gcc dot gnu dot org [this message] 2007-07-22 16:34 ` nathan at gcc dot gnu dot org 2007-07-23 19:24 ` [Bug c++/30818] [4.1/4.2 " rguenth at gcc dot gnu dot org 2008-07-04 21:58 ` [Bug c++/30818] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-30 21:35 ` 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=20070722162605.608.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: linkBe 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).