From: "H . J . Lu" <hjl@lucon.org>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: linux-mips@oss.sgi.com
Subject: Re: gcc-2.96-99 optimization bug?
Date: Fri, 8 Feb 2002 10:30:47 -0800 [thread overview]
Message-ID: <20020208103047.A6079@lucon.org> (raw)
In-Reply-To: <20020208.193731.48536791.nemoto@toshiba-tops.co.jp>; from nemoto@toshiba-tops.co.jp on Fri, Feb 08, 2002 at 07:37:31PM +0900
On Fri, Feb 08, 2002 at 07:37:31PM +0900, Atsushi Nemoto wrote:
> I found gcc 2.96 (gcc-2.96-99.1.mipsel.rpm in H.J.Lu's RedHat 7.1)
> outputs wrong code for this short program.
>
> It seems one 'bnez' in good code (at 4007c4) was lost in bad code.
>
> Is this a know problem? If so, is there any patches available?
>
gcc 3.1 seems fine. No one is working on gcc 2.96. I am working on
a new Linuxx/mips which will use gcc 3.1.
H.J.
next prev parent reply other threads:[~2002-02-08 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 10:37 gcc-2.96-99 optimization bug? Atsushi Nemoto
2002-02-08 18:30 ` H . J . Lu [this message]
2002-02-12 2:03 ` Atsushi Nemoto
-- strict thread matches above, loose matches on Subject: below --
2002-02-08 10:53 Zhang Fuxin
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=20020208103047.A6079@lucon.org \
--to=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=nemoto@toshiba-tops.co.jp \
/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