public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/9050] Can't explicitly specialize C++ constructor templates Date: Sun, 26 Oct 2008 22:02:00 -0000 [thread overview] Message-ID: <20081026220127.15687.qmail@sourceware.org> (raw) In-Reply-To: <bug-9050-2393@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from manu at gcc dot gnu dot org 2008-10-26 22:01 ------- It seems that the problem is cp_parser_template_id fails to parse Y<int> as a template-id because when it does a lookup it finds that Y is just a non-template class and concludes that Y<int> cannot be a template-id. This in turn makes cp_parser_class_name fail to parse Y<int>, which makes cp_parser_constructor_declarator_p return false. No idea how this could be fixed... -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|3.4.3 4.1.2 4.3.0 |3.4.3 4.1.2 4.3.0 4.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9050
next prev parent reply other threads:[~2008-10-26 22:02 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-9050-2393@http.gcc.gnu.org/bugzilla/> 2008-02-11 22:20 ` vlad dot sharanhovich at gmail dot com 2008-02-11 23:44 ` manu at gcc dot gnu dot org 2008-10-26 22:02 ` manu at gcc dot gnu dot org [this message] 2009-11-20 5:17 ` jason at gcc dot gnu dot org 2009-11-21 3:19 ` [Bug c++/9050] [DR 147] " jason at gcc dot gnu dot org 2009-11-21 6:34 ` jason at gcc dot gnu dot org 2009-11-21 6:34 ` jason at gcc dot gnu dot org [not found] <20021223190601.9050.martin@xemacs.org> 2003-05-25 16:51 ` [Bug c++/9050] " pinskia@physics.uc.edu 2003-08-05 15:12 ` reichelt at gcc dot gnu dot org 2004-01-06 13:07 ` reichelt at gcc dot gnu dot org 2004-06-05 18:13 ` pinskia at gcc dot gnu dot org 2004-07-22 17:05 ` chris at pgsql dot com 2004-07-22 18:36 ` bangerth at dealii 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=20081026220127.15687.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).