On 2017-07-20 16:04, Alex Bennée wrote: > I then implement a few random functions using the softfloat3c code. To > keep things clean the helper functions are all in advsimd_helper.c. As > the two implementations are sitting side by side we need to copy the > exception flags back and forth to ensure the virtual FPU state is > correct between operations implemented by both libraries. This can > obviously be removed is an architecture fully transitions to a later > library.
softfloat3a uses a global FPU state. As it is thread local, that should not be a problem as long as we have one thread per VCPU (which is the case with MTTCG). However, how do you plan to handle the switch from one FPU state to another for the architectures using multiple FPU contexts? That concerns at least arm, i386, mips and ppc. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
