public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, larsbj@gullik.net,
	nobody@gcc.gnu.org
Subject: Re: c++/9443: ICE in resolve_scoped_fn_name, at cp/call.c:2604
Date: Tue, 28 Jan 2003 15:36:00 -0000	[thread overview]
Message-ID: <20030128153646.7452.qmail@sources.redhat.com> (raw)

Old Synopsis: ICE when using Boost Signals.
New Synopsis: ICE in resolve_scoped_fn_name, at cp/call.c:2604

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Jan 28 15:36:46 2003
State-Changed-Why:
    Confirmed. I'm not making progress reducing this weird Boost
    stuff to something more tractable and don't have the time
    right now, but at least I can confirm that it crashed
    the compiler:
    
    g/a> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c boost.ice.ii
    boost.ice.ii:33269: error: expected class-name
    boost.ice.ii:33269: error: expected `{'
    boost.ice.ii:33269: error: expected unqualified-id
    boost.ice.ii:33269: error: expected expected `;'
    [... lot's of errors deleted ...]
    boost.ice.ii:40250: internal compiler error: tree check: expected class 't',
       have 'x' (error_mark) in resolve_scoped_fn_name, at cp/call.c:2604
    Please submit a full bug report,
    
    Previous versions of gcc back to 3.0 just get confused by
    earlier errors (so same story), and the preprocessed sources
    don't compile with 2.95 at all.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9443


             reply	other threads:[~2003-01-28 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 15:36 bangerth [this message]
2003-01-29  9:46 Giovanni Bajo
2003-01-31 15:56 Volker Reichelt
2003-01-31 16:16 Volker Reichelt

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=20030128153646.7452.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=larsbj@gullik.net \
    --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: 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).