Terje Mathisen at Norsk Hydro figured out what the algorithm and the wrong table entries were at the time, and published an fdiv() function which used the fdiv instruction but fixed the errors, at around a 25% speed penalty over just using fdiv (which took 39 cycles for double precision, while the Pentium can with optimal code run 2 integer instructions per cycle)
Terje Mathisen at Norsk Hydro figured out what the algorithm and the wrong table entries were at the time, and published an fdiv() function which used the
fdivinstruction but fixed the errors, at around a 25% speed penalty over just usingfdiv(which took 39 cycles for double precision, while the Pentium can with optimal code run 2 integer instructions per cycle)Amusing fact: Windows still ships the command “pentnt” which exists to detect the 1993 FDIV bug, and enable a software workaround if necessary.