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, nobody@gcc.gnu.org,
	thomas@koeller.dyndns.org
Subject: Re: c++/8557: [3.3 regression] error reporting routines re-entered
Date: Wed, 04 Dec 2002 14:44:00 -0000	[thread overview]
Message-ID: <20021204224458.32767.qmail@sources.redhat.com> (raw)

Old Synopsis: ICE compiling binutils-2.13.1
New Synopsis: [3.3 regression] error reporting routines re-entered

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed Dec  4 14:44:58 2002
State-Changed-Why:
    This is the code:
    ------------------------
    void foo (void *, X (*) (void *));
    ------------------------
    on which I get with 3.2.1 and 3.3 (a couple of days old):
    tmp/g> /home/bangerth/bin/gcc-3.3-pre/lib/gcc-lib/i686-pc-linux-gnu/3.*/cc1plus -fpreprocessed tc-ppc.i -quiet -dumpbase tc-ppc.c
    tc-ppc.i:1: error: parse error before `)' token
    tc-ppc.i:1: error: type specifier omitted for parameter `
    Internal compiler error: Error reporting routines re-entered.
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
    
    It compiled fine with 2.95 (i.e. it gave errors, but no ICE).
    
    I believe someone fixed this in the last few days (Gaby?)
    but I need to build a newer gcc to check that. Until then
    I put this into the usual "regression" mode.

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


             reply	other threads:[~2002-12-04 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 14:44 bangerth [this message]
2002-12-04 15:03 bangerth
2002-12-04 15:06 Gabriel Dos Reis

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=20021204224458.32767.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=nobody@gcc.gnu.org \
    --cc=thomas@koeller.dyndns.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).