adbrucker
/
lh-l4v
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

x64 abstract/machine: introduce and use FPUNullState 

The FPU state is opaque, and its null state is not necessary an array of zeroes.
Instead, the null state is a snapshot taken after initialisation.
This commit is contained in:
Gerwin Klein 2018-03-22 14:19:02 +11:00 committed by Joel Beeren
parent f20ec59695
commit 8744fb20d7
3 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
spec/abstract/X64/Machine_A.thy
View File

@ -108,7 +108,7 @@ definition
definition
new_context :: "user_context" where
"new_context \<equiv> UserContext (\<lambda>r. 0) ((\<lambda>r. 0)(CS := selCS3, SS := selDS3, FLAGS := 0x202))"
"new_context \<equiv> UserContext FPUNullState ((\<lambda>r. 0)(CS := selCS3, SS := selDS3, FLAGS := 0x202))"
definition
pptr_base :: "machine_word" where

2
spec/design/skel/X64/RegisterSet_H.thy
View File

@ -20,7 +20,7 @@ context Arch begin global_naming X64_H
definition
newContext :: "user_context"
where
"newContext \<equiv> UserContext (\<lambda>w. 0) ((K 0) aLU initContext)"
"newContext \<equiv> UserContext FPUNullState ((K 0) aLU initContext)"
end
end

3
spec/machine/X64/MachineOps.thy
View File

@ -265,6 +265,9 @@ definition
where
"setFPUState fc \<equiv> modify (\<lambda>s. UserContext fc (user_regs s))"
(* The FPU state is opaque; the null state is a constant snapshot taken after initialisation *)
consts'
FPUNullState :: fpu_state
consts'
initL2Cache_impl :: "unit machine_rest_monad"