The instructions were originally implemented via builtins and
intrinsics so users would have to explicitly opt-in to using
them. This was useful while were validating whether these instructions
should have been merged into the spec proposal. Now that they have
been, we can use normal codegen patterns, so the intrinsics and
builtins are no longer useful.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Unit tests: pass. 60871 tests passed, 0 failed and 726 were skipped.
clang-format: pass.
Build artifacts: console-log.txt, CMakeCache.txt, test-results.xml, diff.json
llvm/lib/Target/WebAssembly/WebAssemblyISelLowering.cpp | ||
---|---|---|
189 | Just curious, what gets assigned we don't do this? I thought the default value was Legal.. |
llvm/lib/Target/WebAssembly/WebAssemblyISelLowering.cpp | ||
---|---|---|
189 | When we don't do this, we get a sequence that does a compare and a select. You're right that the default is Legal for most things, but not for higher-level instructions like these. |
Just curious, what gets assigned we don't do this? I thought the default value was Legal..