From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mike Uhler <uhler@mips.com>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: unaligned load in branch delay slot
Date: Tue, 28 Jan 2003 12:47:50 +0100 [thread overview]
Message-ID: <20030128124750.A25956@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0301281024060.9269-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Tue, Jan 28, 2003 at 10:30:20AM +0100
On Tue, Jan 28, 2003 at 10:30:20AM +0100, Geert Uytterhoeven wrote:
> If it happens, I should get a SIGILL, right?
Right.
Hmm... If you can't reproduce this anymore I guess we should pull this
patch again? Despite Mike basically acknowledging that such behaviour
exists I don't feel to well about applying patches for non-reproducable
processor behaviour and would rather prefer to wait until we believe to
know the full details.
?
> > + set_fs(seg);
>
> `seg' is never initialized?
Yep ...
> > + case bcond_op:
> > + case j_op:
> > + case jal_op:
> > + case beq_op:
> > + case bne_op:
> > + case blez_op:
> > + case bgtz_op:
> > + case beql_op:
> > + case bnel_op:
> > + case blezl_op:
> > + case bgtzl_op:
> > + case jalx_op:
> > + return 1;
>
> I think you can remove the unconditional jumps, cfr. Mike's comments.
That's one of the points where I felt a bit unsafe about the extend of
the issue so I left the jumps in. Anyway, why should it make a difference
if an instruction is conditional or not?
> Isn't the Vr4120A core MIPS32?
Vr4120 is MIPS III.
Ralf
next prev parent reply other threads:[~2003-01-28 11:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 16:13 unaligned load in branch delay slot Geert Uytterhoeven
2003-01-13 17:19 ` Mike Uhler
2003-01-13 17:19 ` Mike Uhler
2003-01-13 18:04 ` Geert Uytterhoeven
2003-01-13 20:12 ` Mike Uhler
2003-01-13 20:12 ` Mike Uhler
2003-01-28 2:39 ` Ralf Baechle
2003-01-28 9:30 ` Geert Uytterhoeven
2003-01-28 11:47 ` Ralf Baechle [this message]
2003-01-28 12:27 ` Geert Uytterhoeven
2003-01-29 1:39 ` Brad Parker
2003-01-29 6:40 ` Ralf Baechle
2003-01-28 12:30 ` Maciej W. Rozycki
2003-01-28 12:54 ` Ralf Baechle
2003-01-28 17:53 ` Jun Sun
2003-01-28 19:48 ` Mike Uhler
2003-01-28 19:48 ` Mike Uhler
2003-01-28 21:30 ` [OT] " justinca
2003-01-28 21:39 ` Mike Uhler
2003-01-28 21:39 ` Mike Uhler
2003-01-29 14:25 ` Ralf Baechle
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=20030128124750.A25956@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=uhler@mips.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