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,
	snyder@fnal.gov
Subject: Re: c/9928: [3.3/3.4 regression] ICE on duplicate enum declaration
Date: Mon, 03 Mar 2003 23:37:00 -0000	[thread overview]
Message-ID: <20030303233728.20210.qmail@sources.redhat.com> (raw)

Old Synopsis: ICE on duplicate enum declaration
New Synopsis: [3.3/3.4 regression] ICE on duplicate enum declaration

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Mar  3 23:37:28 2003
State-Changed-Why:
    Confirmed. With 3.2, we just get an error:
    g/x> /home/bangerth/bin/gcc-3.2.2-pre/bin/gcc -c x.c
    x.c:2: conflicting types for `CODES'
    x.c:1: previous declaration of `CODES'
    
    3.3 bails out, which has of course the same source as 3.4
    ICEing:
    g/x> /home/bangerth/bin/gcc-3.3-pre/bin/gcc -c x.c
    x.c:2: error: conflicting types for `CODES'
    x.c:1: error: previous declaration of `CODES'
    x.c:2: confused by earlier errors, bailing out
    
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -c x.c
    x.c:2: error: conflicting types for `CODES'
    x.c:1: error: previous declaration of `CODES'
    x.c:2: internal compiler error: Segmentation fault
    
    Since 3.2 did not ICE, this is a regression.
    
    W.

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


             reply	other threads:[~2003-03-03 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 23:37 bangerth [this message]
2003-03-11 13:36 Steven Bosscher
2003-03-11 13:56 Eric Botcazou
2003-03-11 14:04 steven
2003-03-12  0:16 Steven Bosscher
2003-03-12 10:14 ebotcazou

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=20030303233728.20210.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=snyder@fnal.gov \
    /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).