loading of wsock32 disturbs FPU

This is a follow-up on thread "1.5.12: FPU affected by gethostname call". It shows that calling some functions of the windows API will affect the floating point unit so that all calculation are performed with double precision only, instead of long double precision. After careful examination, th

Re: 1.5.12: FPU affected by gethostname call

e FP registers are presumably being saved and restored > owing to the call to gethostname, so that's why removing the call fixes it. > > If you use normal doubles, you're only ever working with 64-bit values, > so that's why changing to doubles gets the same result