================
@@ -79,6 +79,19 @@ static bool WantsPthread(const llvm::Triple &Triple, const
ArgList &Args) {
return WantsPthread;
}
+static bool WantsComponentModelThreadContext(const llvm::Triple &Triple, const
ArgList &Args) {
+ // If the target is WASIP3, then enable the
+ // component-model-thread-context feature by default, unless explicitly
+ // disabled.
+ return Triple.getOSName() == "wasip3" &&
----------------
TartanLlama wrote:
Yeah, that makes sense. I've changed it so that the decision is made exactly
once for Clang and once for LLVM. So Clang's driver will explicitly supply
either +context-model-thread-context or -context-model-thread-context to LLVM,
and any users calling `llc` directly or using frontends that don't explicitly
set that feature will also get the correct default.
https://github.com/llvm/llvm-project/pull/175800
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
