public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: ebotcazou@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7675: [3.2/3.3 regression] ICE in fixup_var_refs_1
Date: Tue, 31 Dec 2002 00:26:00 -0000	[thread overview]
Message-ID: <20021231082601.25055.qmail@sources.redhat.com> (raw)

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

From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: <janis187@us.ibm.com>
Cc: <gcc-gnats@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<sowhat@amnis.co.jp>
Subject: Re: optimization/7675: [3.2/3.3 regression] ICE in fixup_var_refs_1
Date: Tue, 31 Dec 2002 09:19:06 +0100

 > Eric, I just noticed that you're working on a patch.  Perhaps
 > this information will be useful for you.
 
 See the analysis and the patch at:
 http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00336.html
 
 Unfortunately, the bug is the consequence of a fundamental problem with
 nested functions in the C front-end, whose right solution is the one
 proposed by Richard:
 http://gcc.gnu.org/ml/gcc-patches/2002-12/msg00367.html
 
 I'll try to address it for 3.4 and, in the meantime, ask Richard what to do
 for the 3.2 and 3.3 branches, in light of you pinpointing Jason's patch.
 
 Thanks.
 
 - Eric
 
 


             reply	other threads:[~2002-12-31  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31  0:26 Eric Botcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-24 12:26 Janis Johnson
2002-12-03  6:06 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=20021231082601.25055.qmail@sources.redhat.com \
    --to=ebotcazou@libertysurf.fr \
    --cc=ebotcazou@gcc.gnu.org \
    --cc=gcc-prs@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).