public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@ticam.utexas.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/9309: [3.4 regression][New parser] ICE with function-pointer-type template arguments
Date: Tue, 14 Jan 2003 15:56:00 -0000	[thread overview]
Message-ID: <20030114154732.7102.qmail@sources.redhat.com> (raw)


>Number:         9309
>Category:       c++
>Synopsis:       [3.4 regression][New parser] ICE with function-pointer-type template arguments
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 14 07:56:02 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Bangerth
>Release:        unknown-1.0
>Organization:
>Environment:
3.4 after parser merge
>Description:
I suspect that this code is illegal, since the template
keyword for disambiguation is not allowed here:
----------------------------
struct CPU {
    typedef int (*pfun)();

    template <pfun step1>
    static int dispatch();
};

template<int>
static int foo();

template int CPU::dispatch<&template foo<2> > ();
------------------------

Nevertheless, it should not ICE, which it started
within the last three weeks, probably with the new parser:

tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/gcc -c y.cc
y.cc:11: error: parse error before `template'

tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -c y.cc
y.cc:11: error: template-id `dispatch<<expression error> >' used as a
   declarator
y.cc:11: internal compiler error: Speicherzugriffsfehler
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-14 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 15:56 bangerth [this message]
2003-01-14 16:09 bangerth

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=20030114154732.7102.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).