Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Hiroyuki Machida <machida@sm.sony.co.jp>
To: bellard@email.enst.fr
Cc: linux-mips@oss.sgi.com
Subject: Re: mips gcc 2.95.2 and 2.91.66 bug
Date: Fri, 09 Mar 2001 11:28:08 +0900	[thread overview]
Message-ID: <20010309112808P.machida@sm.sony.co.jp> (raw)
In-Reply-To: <Pine.GSO.4.02.10103081721360.9471-100000@donjuan.enst.fr>


From: Fabrice Bellard <bellard@email.enst.fr>
Subject: mips gcc 2.95.2 and 2.91.66 bug
Date: Thu, 8 Mar 2001 17:43:31 +0100 (MET)

> Hi!
> 
> Maybe this bug can interest you: when using byte swaping in le16_to_cpu
> for example, mips gcc 2.95.2 and 2.91.66 sometime do not generate correct
> code : the u16 to u32 convertion is missing. I found this bug while
> compiling drivers/mtd/ftl.c in build_maps(). Here is a sample source to
> reproduce the bug:

This bug is fixed by following chage in GCC 3.0. 

gcc/gcc/ChangeLog.3:

2000-04-24  Hiroyuki Machida <machida@sm.sony.co.jp>

        * combine.c (try_combine): Update reg_nonzero_bits of
        newi2pat before newpat.


Please refer mail archives at gcc.gnu.org for details.
You can easily apply this fix to gcc-2.95.x.

---
Hiroyuki Machida
Creative Station		SCE Inc.

      reply	other threads:[~2001-03-09  2:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 16:20 Question concerning Assembler error Jeff Harrell
2001-03-08 16:30 ` H.Heinold
2001-03-08 16:40   ` Ralf Baechle
2001-03-08 16:54     ` Kevin D. Kissell
2001-03-08 16:54       ` Kevin D. Kissell
2001-03-09  0:18       ` Ralf Baechle
2001-03-09  0:18         ` Ralf Baechle
2001-03-08 16:37 ` Ralf Baechle
2001-03-08 16:43 ` mips gcc 2.95.2 and 2.91.66 bug Fabrice Bellard
2001-03-09  2:28   ` Hiroyuki Machida [this message]

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=20010309112808P.machida@sm.sony.co.jp \
    --to=machida@sm.sony.co.jp \
    --cc=bellard@email.enst.fr \
    --cc=linux-mips@oss.sgi.com \
    /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