diff options
| author | Dan Gohman <sunfish@mozilla.com> | 2015-08-21 08:26:54 -0700 |
|---|---|---|
| committer | Dan Gohman <sunfish@mozilla.com> | 2015-08-21 08:26:54 -0700 |
| commit | 773dca0adefcdd44e6cbced6507822c1bfdb94d8 (patch) | |
| tree | df9e2d7bc5165ede2b5896f4549f5f214f56494f /FAQ.md | |
| parent | 5a0c997f03067721eebc5ce4999ea0b2a8726b80 (diff) | |
| parent | fc93b347c35666ee5334e621a076fdbdd167127b (diff) | |
| download | nanowasm-design-773dca0adefcdd44e6cbced6507822c1bfdb94d8.tar.gz | |
Merge pull request #265 from WebAssembly/jit-library
Add a page about a JIT/Optimization library idea.
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -220,7 +220,7 @@ WebAssembly implementations run on the user side, so there is no opportunity for * Many of the important fast-math optimizations happen in the mid-level optimizer of a compiler, before WebAssembly code is emitted. For example, loop vectorization that depends on floating point reassociation can still be done at this level if the user applies the appropriate fast-math flags, so WebAssembly programs can still enjoy these benefits. As another example, compilers can replace floating point division with floating point multiplication by a reciprocal in WebAssembly programs just as they do for other platforms. - * Mid-level compiler optimizations may also be augmented by implementing them in a JIT library in WebAssembly. This would allow them to perform optimizations that benefit from having [information about the target](FeatureTest.md) and information about the source program semantics such as fast-math flags at the same time. For example, if SIMD types wider than 128-bit are added, it's expected that there would be feature tests allowing WebAssembly code to determine which SIMD types to use on a given platform. + * Mid-level compiler optimizations may also be augmented by implementing them in a [JIT library](JITLibrary.md) in WebAssembly. This would allow them to perform optimizations that benefit from having [information about the target](FeatureTest.md) and information about the source program semantics such as fast-math flags at the same time. For example, if SIMD types wider than 128-bit are added, it's expected that there would be feature tests allowing WebAssembly code to determine which SIMD types to use on a given platform. * When WebAssembly [adds an FMA operation](FutureFeatures.md#additional-floating-point-operations), folding multiply and add sequences into FMA operators will be possible. |