aboutsummaryrefslogtreecommitdiff
path: root/EssentialPostV1Features.md
diff options
context:
space:
mode:
authorLuke Wagner <mail@lukewagner.name>2015-05-01 10:41:11 -0500
committerLuke Wagner <mail@lukewagner.name>2015-05-01 10:41:11 -0500
commitc648a04e8dd87a33fa6a63381846aaa16cc1a8ef (patch)
tree1bf3b4d8bacfd86894d3727ed153c629887770a5 /EssentialPostV1Features.md
parent247be80590029da3da1add9705dfe6efe76079ee (diff)
downloadnanowasm-design-c648a04e8dd87a33fa6a63381846aaa16cc1a8ef.tar.gz
Address comments
Diffstat (limited to 'EssentialPostV1Features.md')
-rw-r--r--EssentialPostV1Features.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/EssentialPostV1Features.md b/EssentialPostV1Features.md
index 8305bac..46221aa 100644
--- a/EssentialPostV1Features.md
+++ b/EssentialPostV1Features.md
@@ -19,7 +19,11 @@ in [future versions](FutureFeatures.md).
* Essentially, import [SIMD.js](https://github.com/johnmccutchan/ecmascript_simd).
* Would be statically typed analogous to [SIMD.js-in-asm.js](discourse.specifiction.org/t/request-for-comments-simd-js-in-asm-js).
* The goal is to both reuse specification of op semantics (with TC39) and backend implementation (same IR nodes)
-* Track SIMD.js after v.1.
+ * Track SIMD.js after v.1.
+* SIMD adds new primitive variable/expression types (e.g., `float32x4`) so it has to be part of
+ the core semantics.
+* SIMD operations (e.g., `float32x4.add`) could be either builtin ops (no different than int32 add) or
+ exports of a builtin SIMD module.
## Zero-cost Exception Handling
* Developer access to stack unwinding and inspection.