From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Bug report about udivsi3-0s.S
Date: Mon, 08 Dec 2008 02:33:23 +0000 [thread overview]
Message-ID: <20081208023323.GB8860@linux-sh.org> (raw)
In-Reply-To: <ur64ntkcp.wl%morimoto.kuninori@renesas.com>
Morimoto-san,
On Fri, Dec 05, 2008 at 11:40:54AM +0900, morimoto.kuninori@renesas.com wrote:
> I notice bug of ${LINUX}/arch/sh/lib/udivsi3-0s.
>
> My environment is
>
> gcc : sh4-unknown-linug-gnu-gcc
> OS : Linux 2.6.28-rc6 (from latest git)
> CPU : SH7723
>
> When I use latest Linux 2.6.28-rc6 and sh4-unknown-linug-gnu-gcc,
> kernel starts an infinite loop on sh-sci.c :: sci_set_termios
>
> but it works well when I use sh4-linux-gcc
>
> And I found the reason.
> I think __udivsi3 should not break r1 register.
>
> following is my kernel.
> Kernel starts infinite loop on 88118408.
>
With Yoshii-san's patch in place this should be fixed now, please see if
current git works for you.
next prev parent reply other threads:[~2008-12-08 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 2:40 Bug report about udivsi3-0s.S morimoto.kuninori
2008-12-08 2:33 ` Paul Mundt [this message]
2008-12-08 7:09 ` morimoto.kuninori
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=20081208023323.GB8860@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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