]> git.proxmox.com Git - wasi-libc.git/commit
threads: change `wasm32-wasi-pthread` to `wasm32-wasi-threads` (#381)
authorAndrew Brown <andrew.brown@intel.com>
Fri, 13 Jan 2023 02:56:52 +0000 (18:56 -0800)
committerFabian Grünbichler <f.gruenbichler@proxmox.com>
Wed, 2 Aug 2023 10:24:08 +0000 (12:24 +0200)
commit8b9706b98aaf026f9cbef44ef5d0b150f38fac6c
treec7f80e5fc3f3d8e44ca3c844ddadda8e01ec9b7d
parent9fcc8d48ee6eba2af44d550c5740b5a592acc9f8
threads: change `wasm32-wasi-pthread` to `wasm32-wasi-threads` (#381)

* Change `wasm32-wasi-pthread` to `wasm32-wasi-threads`

After some thought, I think that we should rename the `THREAD_MODEL=posix` build to avoid confusion. Why? Though in this project the use of this target does involve pthreads, it will not be so in other standard libraries or languages (see, e.g., https://github.com/rust-lang/compiler-team/issues/574). I think it would be preferable to emphasize the "threads" Wasm-level proposal and the "wasi-threads" proposal rather than the specific details of which threading API is being exposed.

* fix: rename the `expected` output directory as well
Makefile
expected/wasm32-wasi-pthread/defined-symbols.txt [deleted file]
expected/wasm32-wasi-pthread/include-all.c [deleted file]
expected/wasm32-wasi-pthread/predefined-macros.txt [deleted file]
expected/wasm32-wasi-pthread/undefined-symbols.txt [deleted file]
expected/wasm32-wasi-threads/defined-symbols.txt [new file with mode: 0644]
expected/wasm32-wasi-threads/include-all.c [new file with mode: 0644]
expected/wasm32-wasi-threads/predefined-macros.txt [new file with mode: 0644]
expected/wasm32-wasi-threads/undefined-symbols.txt [new file with mode: 0644]