public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7677: Gcc 3.2 generate the wrong target machine code, TOO, making the target crash
Date: Fri, 20 Sep 2002 13:26:00 -0000	[thread overview]
Message-ID: <20020920202601.5427.qmail@sources.redhat.com> (raw)

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

From: Daniel Jacobowitz <drow@mvista.com>
To: lium@i-net.com.cn, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	wxf@start.com.cn
Cc: Richard Earnshaw <rearnsha@arm.com>
Subject: Re: c/7677: Gcc 3.2 generate the wrong target machine code, TOO, making the target crash
Date: Fri, 20 Sep 2002 16:25:20 -0400

 I believe this bug is fixed on the GCC 3.2 branch now, by the same patch
 that fixed optimization/7967.
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2002-09-20 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 13:26 Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-21  4:09 rearnsha
2002-08-21  8:36 lium

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=20020920202601.5427.qmail@sources.redhat.com \
    --to=drow@mvista.com \
    --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).