public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: giovannibajo@libero.it
To: gcc-gnats@gcc.gnu.org
Subject: c++/10583: [3.4 regression] ICE with missing typename to refer to nested struct
Date: Thu, 01 May 2003 17:26:00 -0000	[thread overview]
Message-ID: <20030501171950.14625.qmail@sources.redhat.com> (raw)


>Number:         10583
>Category:       c++
>Synopsis:       [3.4 regression] ICE with missing typename to refer to nested struct
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Thu May 01 17:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Giovanni Bajo
>Release:        3.4 CVS 20030430
>Organization:
>Environment:
i686-pc-cygwin
>Description:
The following snippet triggers an ICE on the mainline:

----------------------------------
template <typename> 
struct A 
{
    struct B 
    {};
};

template <typename T> 
void func(A<T>::B* )
{
}

int main() 
{
   func<void>(0);
}
----------------------------------
regr3.cpp:9: error: variable or field `func' declared void
regr3.cpp:9: error: template declaration of `int func'
regr3.cpp:9: error: expected primary-expression
regr3.cpp:10: error: expected `;'
regr3.cpp: In function `int main()':
regr3.cpp:15: internal compiler error: in cp_parser_template_id, at cp/parser.c:8013
Please submit a full bug report,


The code is illegal (it's missing a typename), but the compiler should not ICE anyway. Moreover, the error message is _very_ confusing.
>How-To-Repeat:

>Fix:
Fix the code adding a typename in front of A<T>::B.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-05-01 17:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030501171950.14625.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-gnats@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).