cpu.x86.64: define jit-load-vm as a no-op
This was the signal handler prolog code can be shared completely between x86.32 and x86.64.db4
parent
842eb27785
commit
b321c5656e
|
@ -38,6 +38,11 @@ IN: bootstrap.x86
|
||||||
0 JMP f rc-relative rel-word-pic-tail
|
0 JMP f rc-relative rel-word-pic-tail
|
||||||
] jit-word-jump jit-define
|
] jit-word-jump jit-define
|
||||||
|
|
||||||
|
: jit-load-vm ( -- )
|
||||||
|
! no-op on x86-64. in factor contexts vm-reg always contains the
|
||||||
|
! vm pointer.
|
||||||
|
;
|
||||||
|
|
||||||
: jit-load-context ( -- )
|
: jit-load-context ( -- )
|
||||||
ctx-reg vm-reg vm-context-offset [+] MOV ;
|
ctx-reg vm-reg vm-context-offset [+] MOV ;
|
||||||
|
|
||||||
|
|
|
@ -104,9 +104,7 @@ big-endian off
|
||||||
|
|
||||||
PUSHF
|
PUSHF
|
||||||
|
|
||||||
! on x86-32 we need to load the vm register
|
jit-load-vm ;
|
||||||
! on x86-64 it's already loaded whenever we're in a factor context
|
|
||||||
bootstrap-cell 4 = [ jit-load-vm ] when ;
|
|
||||||
|
|
||||||
: jit-signal-handler-epilog ( -- )
|
: jit-signal-handler-epilog ( -- )
|
||||||
POPF
|
POPF
|
||||||
|
|
Loading…
Reference in New Issue