Finn Thain dixit:
>Losing a register also hurts performance. Someone suggested moving
Right, but at least m68k is not as register-starved as i386.
And when changing the ABI “anyway”, we could do other sensible
things (64-bit time_t, register passing of arguments, other
legacy cleanup).
>get/set_thread_area to a VDSO (as well as the atomic ops). As I understand
>it, this need not break the ABI and should be faster than the TLS system
>calls.
It will not break the ABI, but how’d it work?
• One kernel/user shared, readonly, page global (for time, atomic)
• One kernel/user shared page per thread (instead of process),
for TLS (and possibly random)?
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.bsm.4.64l.1308220807460.23...@herc.mirbsd.org
