public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: oldham@codesourcery.com
To: gcc-gnats@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: c++/10762: parser failure on illegal templated type declared with 'using'
Date: Tue, 13 May 2003 02:06:00 -0000	[thread overview]
Message-ID: <20030513015730.17239.qmail@sources.redhat.com> (raw)


>Number:         10762
>Category:       c++
>Synopsis:       parser failure on illegal templated type declared with 'using'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Tue May 13 02:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Jeffrey D. Oldham
>Release:        development
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
goo.cc: In function `int main()':
goo.cc:7: internal compiler error: in cp_parser_lookup_name, at cp/parser.c:
   13222
Please submit a full bug report,

The code is illegal because 'template-id's are not permitted in using declarations.  The parser does not catch this until this illegal type is used.
>How-To-Repeat:
g++ goo.cc
>Fix:
unknown
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="goo.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="goo.cc"

bmFtZXNwYWNlIE4gewogIHRlbXBsYXRlIDx0eXBlbmFtZSBUPgogIHN0cnVjdCBmb28ge307Cn0K
CmludCBtYWluKCkgewogIHVzaW5nIE46OmZvbzxkb3VibGU+CgogIGZvbzxkb3VibGU+IGM7Cgog
IHJldHVybiAwOwp9Cg==


             reply	other threads:[~2003-05-13  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  2:06 oldham [this message]
2003-05-13  5:36 Dara Hazeghi

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=20030513015730.17239.qmail@sources.redhat.com \
    --to=oldham@codesourcery.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).