diff options
| author | JF Bastien <github@jfbastien.com> | 2016-01-04 11:24:45 -0800 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2016-01-04 11:24:45 -0800 |
| commit | 95f3e51691d865a0429bd579cce4918dfe27aef1 (patch) | |
| tree | d2177768af7cf3ffc79b6b6ed34a8b6b5a7bd51b | |
| parent | a9b0fd332b67d1aaff723a3d57b52f39be80dece (diff) | |
| download | binaryen-95f3e51691d865a0429bd579cce4918dfe27aef1.tar.gz binaryen-95f3e51691d865a0429bd579cce4918dfe27aef1.tar.bz2 binaryen-95f3e51691d865a0429bd579cce4918dfe27aef1.zip | |
Typo
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -167,7 +167,7 @@ The `check.py` script supports some options: * If an interpreter is provided, we run the output through it, checking for parse errors. * If tests are provided, we run exactly those. If none are provided, we run them all. * Some tests require `emcc` or `nodejs` in the path. They will not run if the tool cannot be found, and you'll see a warning. - * We have tests from upstream in `tests/spec` and `tests/experimental`, in git submodules. Running `./pudate.py` should update those. + * We have tests from upstream in `tests/spec` and `tests/experimental`, in git submodules. Running `./update.py` should update those. (`src/emscripten-optimizer` is synced with `tools/optimizer/` in the main emscripten repo, for convenience) |