linux-mips
[Top] [All Lists]

Illegal instruction - a workaround or fix ?

To: linux-mips@oss.sgi.com
Subject: Illegal instruction - a workaround or fix ?
From: Florian Lohoff <flo@rfc822.org>
Date: Sun, 11 Mar 2001 19:16:39 +0100
Organization: rfc822 - pure communication
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
Hi,
i seem to get the illegal instruction stuff killed when
doing this.

diff -u -r1.17 sysmips.c
--- arch/mips/kernel/sysmips.c  2001/02/09 21:05:46     1.17
+++ arch/mips/kernel/sysmips.c  2001/03/11 16:11:30
@@ -111,13 +111,14 @@
 
                ((struct pt_regs *)&cmd)->regs[2] = tmp;
                ((struct pt_regs *)&cmd)->regs[7] = 0;
-
+#if 0
                __asm__ __volatile__(
                        "move\t$29, %0\n\t"
                        "j\to32_ret_from_sys_call"
                        : /* No outputs */
                        : "r" (&cmd));
                /* Unreached */
+#endif
        }
 
        case MIPS_FIXADE:


Could someone please explain me the difference betweeen "handle_sys"
which leads to "o32_ret_from_sys_call" and ... which leads to
"ret_from_sys_call".

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?


<Prev in Thread] Current Thread [Next in Thread>