UpsilonNumworks/Upsilon
1
0
Fork 0
mirror of https://github.com/UpsilonNumworks/Upsilon.git synced 2026-03-18 21:30:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

[liba] More detailed README for the externals

Browse Source 
Change-Id: I9c5c4d9e86933aa81e3f45048bb004acafed41bc
This commit is contained in:
Romain Goyet
2017-08-03 14:59:34 +02:00
parent c84b378b8b
commit f21428e20f
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
liba/src/external/README.txt vendored
View File

@@ -1,2 +1,15 @@
"softfloat": Unaltered files from SoftFloat v3c.
http://www.jhauser.us/arithmetic/SoftFloat.html
"openbsd": Unaltered files from OpenBSD 6.0. Original path is "lib/libm/src"
"openbsd/include": Compatibility headers needed to build files from OpenBSD.
http://www.openbsd.org
Why use OpenBSD's libm? First and foremost, nearly everyone use fdlibm in a way
or another, and OpenBSD is no exception. That being said, OpenBSD comes with a
single-precision variant (which fdlibm itself lacks). And more interestingly,
this variant does all its computation in single-precision (it never upgrades to
double-precision). In our case, this is very interesting because we're doing
single-precision computation when we better performance at the cost of accuracy,
and in our cse our hardware has a single-precision FPU so switching to double
can yield much lower performances.