From: lamont@smallone.fc.hp.com (LaMont Jones)
To: parisc-linux@parisc-linux.org
Cc: lamont@hp.com
Subject: [parisc-linux] unaligned.c oops
Date: Thu, 2 Oct 2003 15:10:48 -0600 [thread overview]
Message-ID: <20031002211048.GA819@smallone.fc.hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 104 bytes --]
The following patch should make the unaligned handler work better.
(float ops were miscoded...)
lamont
[-- Attachment #2: unaligned.diff --]
[-- Type: text/plain, Size: 1457 bytes --]
Index: unaligned.c
===================================================================
RCS file: /var/cvs/linux-2.4/arch/parisc/kernel/unaligned.c,v
retrieving revision 1.21
diff -u -r1.21 unaligned.c
--- unaligned.c 23 Sep 2003 20:15:33 -0000 1.21
+++ unaligned.c 2 Oct 2003 21:09:02 -0000
@@ -93,13 +93,17 @@
#define OPCODE_STDA OPCODE1(0x03,1,0xf)
#define OPCODE_FLDWX OPCODE1(0x09,0,0x0)
-#define OPCODE_FSTWX OPCODE1(0x09,0,0x4)
+#define OPCODE_FLDWXR OPCODE1(0x09,0,0x1)
+#define OPCODE_FSTWX OPCODE1(0x09,0,0x8)
+#define OPCODE_FSTWXR OPCODE1(0x09,0,0x9)
#define OPCODE_FLDWS OPCODE1(0x09,1,0x0)
-#define OPCODE_FSTWS OPCODE1(0x09,1,0x4)
+#define OPCODE_FLDWSR OPCODE1(0x09,1,0x1)
+#define OPCODE_FSTWS OPCODE1(0x09,1,0x8)
+#define OPCODE_FSTWSR OPCODE1(0x09,1,0x9)
#define OPCODE_FLDDX OPCODE1(0x0b,0,0x0)
-#define OPCODE_FSTDX OPCODE1(0x0b,0,0x4)
+#define OPCODE_FSTDX OPCODE1(0x0b,0,0x8)
#define OPCODE_FLDDS OPCODE1(0x0b,1,0x0)
-#define OPCODE_FSTDS OPCODE1(0x0b,1,0x4)
+#define OPCODE_FSTDS OPCODE1(0x0b,1,0x8)
#define OPCODE_LDD_L OPCODE2(0x14,0)
#define OPCODE_FLDD_L OPCODE2(0x14,1)
@@ -541,6 +545,8 @@
case OPCODE_FLDWX:
case OPCODE_FLDWS:
+ case OPCODE_FLDWXR:
+ case OPCODE_FLDWSR:
flop=1;
ret = emulate_ldw(regs,FR3(regs->iir),1);
break;
@@ -553,6 +559,8 @@
case OPCODE_FSTWX:
case OPCODE_FSTWS:
+ case OPCODE_FSTWXR:
+ case OPCODE_FSTWSR:
flop=1;
ret = emulate_stw(regs,FR3(regs->iir),1);
break;
reply other threads:[~2003-10-02 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031002211048.GA819@smallone.fc.hp.com \
--to=lamont@smallone.fc.hp.com \
--cc=lamont@hp.com \
--cc=parisc-linux@parisc-linux.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