1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 NetWinder Floating Point Emulator
5 (c) 1998, 1999 Philip Blundell
7 Direct questions, comments to Scott Bambrough <scottb@netwinder.org>
10 #include <asm/assembler.h>
11 #include <asm/opcodes.h>
13 /* This is the kernel's entry point into the floating point emulator.
14 It is called from the kernel with code similar to this:
17 ldrt r0, [r4] @ r0 = instruction
18 adrsvc al, r9, ret_from_exception @ r9 = normal FP return
19 adrsvc al, lr, fpundefinstr @ lr = undefined instr return
23 strb r8, [r10, #TSK_USED_MATH] @ set current->used_math
24 add r10, r10, #TSS_FPESAVE @ r10 = workspace
26 ldr pc, [r4] @ Call FP emulator entry point
28 The kernel expects the emulator to return via one of two possible
29 points of return it passes to the emulator. The emulator, if
30 successful in its emulation, jumps to ret_from_exception (passed in
31 r9) and the kernel takes care of returning control from the trap to
32 the user code. If the emulator is unable to emulate the instruction,
33 it returns via _fpundefinstr (passed via lr) and the kernel halts the
34 user program with a core dump.
36 On entry to the emulator r10 points to an area of private FP workspace
37 reserved in the thread structure for this process. This is where the
38 emulator saves its registers across calls. The first word of this area
39 is used as a flag to detect the first time a process uses floating point,
40 so that the emulator startup cost can be avoided for tasks that don't
43 This routine does three things:
45 1) The kernel has created a struct pt_regs on the stack and saved the
46 user registers into it. See /usr/include/asm/proc/ptrace.h for details.
48 2) It calls EmulateAll to emulate a floating point instruction.
49 EmulateAll returns 1 if the emulation was successful, or 0 if not.
51 3) If an instruction has been emulated successfully, it looks ahead at
52 the next instruction. If it is a floating point instruction, it
53 executes the instruction, without returning to user space. In this
54 way it repeatedly looks ahead and executes floating point instructions
55 until it encounters a non floating point instruction, at which time it
56 returns via _fpreturn.
58 This is done to reduce the effect of the trap overhead on each
59 floating point instructions. GCC attempts to group floating point
60 instructions to allow the emulator to spread the cost of the trap over
61 several floating point instructions. */
63 #include <asm/asm-offsets.h>
67 mov r4, lr @ save the failure-return addresses
68 mov sl, sp @ we access the registers via 'sl'
70 ldr r5, [sp, #S_PC] @ get contents of PC;
71 mov r6, r0 @ save the opcode
73 ldr r1, [sp, #S_PSR] @ fetch the PSR
74 bl arm_check_condition @ check the condition
75 cmp r0, #ARM_OPCODE_CONDTEST_PASS @ condition passed?
77 @ if condition code failed to match, next insn
78 bne next @ get the next instruction;
80 mov r0, r6 @ prepare for EmulateAll()
81 bl EmulateAll @ emulate the instruction
82 cmp r0, #0 @ was emulation successful
83 reteq r4 @ no, return failure
87 .Lx1: ldrt r6, [r5], #4 @ get the next instruction and
90 and r2, r6, #0x0F000000 @ test for FP insns
94 retne r9 @ return ok if not a fp insn
96 str r5, [sp, #S_PC] @ update PC copy in regs
98 mov r0, r6 @ save a copy
99 b emulate @ check condition and emulate
101 @ We need to be prepared for the instructions at .Lx1 and .Lx2
102 @ to fault. Emit the appropriate exception gunk to fix things up.
103 @ ??? For some reason, faults can happen at .Lx2 even with a
104 @ plain LDR instruction. Weird, but it seems harmless.
105 .pushsection .text.fixup,"ax"
107 .Lfix: ret r9 @ let the user eat segfaults
110 .pushsection __ex_table,"a"