[PATCH] D50423: [WebAssembly] Gate i64x2 and f64x2 on -wasm-enable-unimplemented

Thomas Lively via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed Aug 8 11:24:55 PDT 2018


tlively marked an inline comment as done.
tlively added inline comments.


================
Comment at: lib/Target/WebAssembly/WebAssemblyTargetMachine.cpp:49
+    cl::desc("Emit potentially-unimplemented WebAssembly instructions"),
+    cl::init(false));
+
----------------
aheejin wrote:
> Are we planning to use this flag only for simd or also for other instructions? For example, exception handling is not currently implemented in the VM yet, but we are adding opcodes for it (under `-mattr=+exception-handling` flag). And in case if other stage 0~1 proposals come up, we may want to add them in the toolchain before they are implemented in the VM. Are we gonna use this flag for all these cases? If not, how about changing it to `wasm-enable-unimplemented-simd`?
It may make sense to use the same flag for all cases where ops are implemented in the toolchain but not the VM. However, I'd be happy to change the name if this will only be used for SIMD. Would you want to have a single general flag for this use case, or are other existing mechanisms sufficient?


Repository:
  rL LLVM

https://reviews.llvm.org/D50423





More information about the llvm-commits mailing list