diff options
author | Alon Zakai <alonzakai@gmail.com> | 2019-02-15 14:32:45 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-02-15 14:32:45 -0800 |
commit | 8b820ed0021ab1a6ad5dad3972cfbf2cecb77e45 (patch) | |
tree | acbefada60a23318dde2fdc7f3cac428e80d8e1e /test/example/small_vector.cpp | |
parent | 90d0ee4337c56ce4b30a6cb2a931ae814d150ee7 (diff) | |
download | binaryen-8b820ed0021ab1a6ad5dad3972cfbf2cecb77e45.tar.gz binaryen-8b820ed0021ab1a6ad5dad3972cfbf2cecb77e45.tar.bz2 binaryen-8b820ed0021ab1a6ad5dad3972cfbf2cecb77e45.zip |
if no output is specified to wasm-opt, warn that we are emitting nothing (#1908)
A user that just does
```
wasm-opt input.wasm -O
```
may assume that the input file should have been optimized. But without `-o` we don't emit any output.
Often you may not want any output, like if you just want to run a pass like `--metrics`. But for most users wasm-opt is probably going to be used as an optimizer of files. So this PR suggests we emit a warning in that case.
For comparison, `llvm-opt` would print to the console, but it avoids printing a binary there so it issues a warning. Instead of this warning, perhaps we should do the same? That would also not be confusing.
Closes #1907
Diffstat (limited to 'test/example/small_vector.cpp')
0 files changed, 0 insertions, 0 deletions