Lines Matching full:which

26 which was my 80387 emulator for early versions of djgpp (gcc under
27 msdos); wm-emu387 was in turn based upon emu387 which was written by
61     is not the obvious one which most people seem to use, but is designed
64     seen it. It is based upon one of those ideas which one carries around
74     a value of pi which is accurate to more than 128 bits. As a consequence,
78     80486, which uses a value of pi which is accurate to 66 bits.
87 variables. The code which accesses user memory is confined to five
97 form of re-entrancy which is required by the Linux kernel.
103 are fewer than those which applied to the 1.xx series of the emulator.
139 able to find the instruction which caused the device-not-present
148 check the addressing, and which runs successfully in real mode,
166 which require most computation. The simple instructions are adversely
195 The following results show the improvement which is obtained under
242 precision of the argument x; e.g. an argument of pi/2-(1e-10) which is
273 for pi which is accurate to more than 128 bits precision. As a
288 It is possible with some effort to find very large arguments which
293 have a value of pi which had about 150 bits precision. The FPU
296 0.01059, which in relative terms is hopelessly inaccurate.
298 For arguments close to critical angles (which occur at multiples of
307 worst-case results which are better than the worst-case results given
317 results which are in error (i.e. less accurate than the best possible
318 result (which is 64 bits)) for about one per cent of all arguments
320 frequency of results which are in error.  The last two columns give
321 the worst accuracy which was found (in bits) and the approximate value
322 of the argument which produced it.
339 following table gives the results which were obtained with an AMD
346 instructions return results which are in error for more than 10
361 accuracy of the results were less than 62 bits, which occurs quite