public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/3869: Segmentation fault on specialized outer template with inner member template. Date: Fri, 03 Jan 2003 12:06:00 -0000 [thread overview] Message-ID: <20030103120604.14455.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/3869; it has been noted by GNATS. From: Paolo Carlini <pcarlini@unitus.it> To: Neil Booth <neil@daikokuya.co.uk> Cc: jhl@sssonline.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, fluxsmith@fluxsmith.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/3869: Segmentation fault on specialized outer template with inner member template. Date: Fri, 03 Jan 2003 13:00:39 +0100 Neil Booth wrote: >Paolo Carlini wrote:- > > >>With current 3.4 no segmentation fault, but instead: >> >>3869.cc:14: error: expected unqualified-id >>3869.cc:17: error: expected init-declarator >>3869.cc:17: error: expected `,' or `;' >> >>If the illegal testcase is changed from: >> >> typedef typename Outer<flag>::Inner<int>::Result Result; >> >>to >> >> typedef typename Outer<flag>::template Inner<int>::Result Result; >> >>It is compiled just fine with 3.2, 3.3 and mainline. >> >>It seems to me that the PR can be closed. >>Paolo. >> >> >If so, please add a testcase. > Well, if my analysis is correct, which one? I mean, the legal-ized version is compiled just fine by 3.2.1, 3.3 and 3.4, the illegal one doesn't ICE with 3.4 but, good, is not compiled either (see above). So, perhaps just closing it would be fine? Thanks, Paolo.
next reply other threads:[~2003-01-03 12:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-03 12:06 Paolo Carlini [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-03 12:19 paolo 2003-01-03 12:16 Neil Booth 2003-01-02 21:56 Neil Booth 2003-01-02 21:26 Paolo Carlini 2002-11-01 12:46 Wolfgang Bangerth 2001-08-01 5:19 nathan 2001-07-29 13:06 fluxsmith
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=20030103120604.14455.qmail@sources.redhat.com \ --to=pcarlini@unitus.it \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).