aboutsummaryrefslogtreecommitdiff
path: root/FAQ.md
diff options
context:
space:
mode:
authorDan Gohman <sunfish@mozilla.com>2015-07-17 19:33:04 -0700
committerDan Gohman <sunfish@mozilla.com>2015-07-17 19:33:04 -0700
commit021bd5681d533aba75540ecef20e68030e84dd7f (patch)
tree6a79645b375dd088d1fbd94ad6c17be76a5b5e24 /FAQ.md
parent059681d5dc1b8d65576735f8e4b2c2a2d4809cef (diff)
downloadnanowasm-design-021bd5681d533aba75540ecef20e68030e84dd7f.tar.gz
Add code quotes.
Diffstat (limited to 'FAQ.md')
-rw-r--r--FAQ.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/FAQ.md b/FAQ.md
index 5135b79..127d736 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -222,7 +222,7 @@ WebAssembly implementations run on the user side, so there is no opportunity for
* When WebAssembly [adds an FMA operation](FutureFeatures.md#additional-floating-point-operations), folding multiply and add sequences into FMA operators will be possible.
- * WebAssembly doesn't include its own math functions like sin, cos, exp, pow, and so on. WebAssembly's strategy for such functions is to allow them to be implemented as library routines in WebAssembly itself (note that x86's sin and cos instructions are slow and imprecise and are generally avoided these days anyway). Users wishing to use faster and less precise math functions on WebAssembly can simply select a math library implementation which does so.
+ * WebAssembly doesn't include its own math functions like `sin`, `cos`, `exp`, `pow`, and so on. WebAssembly's strategy for such functions is to allow them to be implemented as library routines in WebAssembly itself (note that x86's `sin` and `cos` instructions are slow and imprecise and are generally avoided these days anyway). Users wishing to use faster and less precise math functions on WebAssembly can simply select a math library implementation which does so.
* Most of the individual floating point operations that WebAssembly does have already map to individual fast instructions in hardware. Telling `add`, `sub`, or `mul` they don't have to worry about NaN for example doesn't make them any faster, because NaN is handled quickly and transparently in hardware on all modern platforms.