I agree, but I don't see these goals as mutually exclusive with "faster syscalls"
-
-
Replying to @whitequark @scanlime
it really depends on architecture--I don't know why x86 went with xsave/xrestor instead of register windows for syscalls
1 reply 0 retweets 1 like -
-
Replying to @FioraAeterna @scanlime
well, not quite, just two sets for user and kernel mode (maybe a third for hypervisor)
2 replies 0 retweets 2 likes -
With good ABI you wouldn't need that. Syscalls would have same call-saved/clobbered contract as function calls.
1 reply 0 retweets 0 likes
Replying to @RichFelker @whitequark and
The whole register save/restore cost comes from all registers being call-saved in the syscall ABI.
7:39 PM - 1 Mar 2018
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.