[clang] [libunwind] [llvm] [wasm] Toolchain support for `wasm32-wali-linux-musl` target (PR #156087)

Heejin Ahn via llvm-commits llvm-commits at lists.llvm.org
Thu Sep 4 18:57:08 PDT 2025


================
@@ -199,6 +199,7 @@ class Triple {
     SUSE,
     OpenEmbedded,
     Intel,
+    WALI,
----------------
aheejin wrote:

It being a vendor seems weird because the current list of vendors basically only include companies.

> think to minimize `cfg` changes and have quick support to the ecosystem, `target_os` would have to be `linux` and `target_env` would have to be `musl`

What is `cfg`? This sounds like making this as a host environment will make something inconvenient. Is that the case?

> If there really is no constraint, I would opt for just dropping `wali` in vendor/environment altogether

Do all changes in this PR, including the specifications of the type sizes, apply to musl in general?

@dschuff WDYT?

https://github.com/llvm/llvm-project/pull/156087


More information about the llvm-commits mailing list