From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
linux-mips@fnet.fr, linux-mips@oss.sgi.com,
Dominic Sweetman <dom@algor.co.uk>
Subject: Re: load_unaligned() and "uld" instruction
Date: Fri, 06 Oct 2000 18:24:29 -0700 [thread overview]
Message-ID: <39DE7B4D.8514FC59@mvista.com> (raw)
In-Reply-To: 20001006182821.B9061@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Thu, Oct 05, 2000 at 09:32:41PM -0700, Jun Sun wrote:
>
> > > > > > Ralf, before the perfect solution is found, the following patch makes
> > > > > > the gcc complain go away. It just use ".set mips3" pragma.
> > >
> > > Which, as Ralf correctly observes, will generate code that will
> > > crash on 32-bit CPUs,
> >
> > Why will it crash 32-bit CPUs? On my R5432 CPU, the lwl/lwr sequence
> > executes just fine.
>
> That's a 64-bit CPU with a 32-bit bus ...
>
That is what the manual claims. However I did find something strange.
I run the following code on R5432:
0x8019dc34 <my_get_unaligned+4>: ldl $a2,7($a0)
0x8019dc38 <my_get_unaligned+8>: ldr $a2,0($a0)
0x8019dc3c <my_get_unaligned+12>: srl $a2,$a2,0x10
As Kevin has guessed, it actually runs fine. However, the register
content in $a2 is not right. Basically it appears that $a2 is a 32-bit
register instead of 64-bit register. I put a srl instruction to make
sure I was not fooled by gdb.
I know R5432 is derived from R5000 FOR 32-bit systems. I guess there
are probably a lot of short-cuts for 64-bit operations.
Jun
next prev parent reply other threads:[~2000-10-06 21:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-25 18:48 load_unaligned() and "uld" instruction Jun Sun
2000-09-25 21:16 ` Dominic Sweetman
2000-09-25 21:36 ` Jun Sun
2000-09-25 23:29 ` Ralf Baechle
2000-09-26 6:22 ` Kevin D. Kissell
2000-09-26 6:22 ` Kevin D. Kissell
2000-09-26 9:08 ` Dominic Sweetman
2000-09-26 9:08 ` Dominic Sweetman
2000-09-29 17:22 ` Ralf Baechle
2000-10-09 14:49 ` Dominic Sweetman
2000-09-26 18:04 ` Jun Sun
2000-09-27 10:06 ` Maciej W. Rozycki
2000-10-06 0:43 ` Ralf Baechle
2000-10-06 9:54 ` Maciej W. Rozycki
2000-10-06 16:21 ` Ralf Baechle
2000-10-05 12:13 ` Ralf Baechle
2000-10-06 1:11 ` Jun Sun
2000-10-05 19:41 ` Kevin D. Kissell
2000-10-05 19:41 ` Kevin D. Kissell
2000-10-06 4:32 ` Jun Sun
2000-10-05 22:10 ` Kevin D. Kissell
2000-10-05 22:10 ` Kevin D. Kissell
2000-10-06 5:53 ` Jun Sun
2000-10-05 23:14 ` Kevin D. Kissell
2000-10-05 23:14 ` Kevin D. Kissell
2000-10-06 16:32 ` Ralf Baechle
2000-10-07 1:35 ` Jun Sun
2000-10-06 22:26 ` Ralf Baechle
2000-10-06 16:28 ` Ralf Baechle
2000-10-07 1:24 ` Jun Sun [this message]
2000-10-06 20:46 ` Kevin D. Kissell
2000-10-06 20:46 ` Kevin D. Kissell
2000-10-07 7:16 ` Jun Sun
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=39DE7B4D.8514FC59@mvista.com \
--to=jsun@mvista.com \
--cc=dom@algor.co.uk \
--cc=kevink@mips.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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