diff options
| author | dann toliver <gh@mrmuster.com> | 2015-06-20 00:07:25 -0400 |
|---|---|---|
| committer | dann toliver <gh@mrmuster.com> | 2015-06-20 00:07:25 -0400 |
| commit | d8f7f19fcd8f6a1617089fe7b0efecdb19fee736 (patch) | |
| tree | 47935d8b389f3b62f795e968e2411838e358f452 /FAQ.md | |
| parent | 3cdd4cf1942bce8c68e82582e0a6ed76464e2b94 (diff) | |
| download | nanowasm-design-d8f7f19fcd8f6a1617089fe7b0efecdb19fee736.tar.gz | |
Update FAQ.md
Two typo fixes
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -182,7 +182,7 @@ WebAssembly has several requirements and goals for its IR and binary encoding: * Fast decoding: The binary format should be fast to decompress and decode for fast startup of programs. * Fast compiling: The IR should be fast to compile (and suitable for either AOT- or JIT-compilation) for fast startup of programs. - * Minimal [nondeterminsim](Nondeterminism.md): The behavior of programs should be as predictable and + * Minimal [nondeterminism](Nondeterminism.md): The behavior of programs should be as predictable and deterministic as possible (and should be the same on every architecture, a stronger form of the portability requirement stated above). @@ -204,7 +204,7 @@ with reduced undefined behavior, and a stable version of the bitcode encoding. I techniques to improve startup performance. However, each customization, workaround, and special solution means less benefit from the common infrastructure. We believe that by taking our experience with LLVM and designing an IR and binary encoding for our goals and requirements, we can do much better than adapting a -system desgined for other purposes. +system designed for other purposes. Note that this discussion applies to use of LLVM IR as a standardized format. LLVM's clang frontend and midlevel optimizers can still be used to generate WebAssembly code from C and C++, and will use |