public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9163: [3.3/3.4 regression] ICE in genrtl_compound_stmt at c-semantics.c:776 with c99 mode
Date: Mon, 24 Mar 2003 00:36:00 -0000	[thread overview]
Message-ID: <20030324001600.27537.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/9163; it has been noted by GNATS.

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	ehrhardt@mathematik.uni-ulm.de, nobody@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, jason@redhat.com
Cc:  
Subject: Re: c/9163: [3.3/3.4 regression] ICE in genrtl_compound_stmt at c-semantics.c:776
 with c99 mode
Date: Mon, 24 Mar 2003 01:12:09 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9163
 
 I haven't checked to make sure, but this patch:
 
 2002-01-22  Jason Merrill  <jason@redhat.com>
 
         * c-semantics.c (genrtl_compound_stmt): Only check nesting
         consistency if this COMPOUND_STMT is scoped.
 
 is obvioulsy by far the most likely candidate for
 this breakage.
 
 Greetz
 Steven
 


             reply	other threads:[~2003-03-24  0:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24  0:36 Steven Bosscher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 16:06 Wolfgang Bangerth
2003-01-07 15:16 Wolfgang Bangerth
2003-01-07 14:16 Christian Ehrhardt
2003-01-07 11:46 Eric Botcazou
2003-01-07 10:16 Christian Ehrhardt
2003-01-07  1:18 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=20030324001600.27537.qmail@sources.redhat.com \
    --to=s.bosscher@student.tudelft.nl \
    --cc=gcc-prs@gcc.gnu.org \
    --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).