diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-17 09:10:43 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-17 09:10:43 +0200 |
| commit | f2ec263023649e596c5076df32c2d328bc9393d2 (patch) | |
| tree | 5dd86caab46e552bd2e62bf9c4fb1a7504a44db4 /results/scraper/fex/173 | |
| parent | 63d2e9d409831aa8582787234cae4741847504b7 (diff) | |
| download | qemu-analysis-main.tar.gz qemu-analysis-main.zip | |
Diffstat (limited to 'results/scraper/fex/173')
| -rw-r--r-- | results/scraper/fex/173 | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/results/scraper/fex/173 b/results/scraper/fex/173 new file mode 100644 index 000000000..200abd850 --- /dev/null +++ b/results/scraper/fex/173 @@ -0,0 +1,12 @@ +Bit accurate Transcendental support +This is a long term goal. +Currently we don't offer bit accurate transcendental instructions. +Reciprocal and reciprocal square root instructions have a fairly large range for their precision support. +These are currently implemented with float divisions to ensure all of the CPU backends match results and have same unit test results. + +These precision differences have the fun quirk that usually something like the reciprocal of 1.0f results in a result that isn't 1.0f even. + +We should have support for a few modes once this gets worked on. +1) Bit accurate representation that matches *SOME* known hardware +2) Most accurate representation (What we have now) +3) Accuracy that falls within x86 precision requirements, but doesn't match any known hardware (In case any device supports less accurate results that are still within x86 spec) \ No newline at end of file |