More accurate explanation of wasm32 state in readme (#776)
authorHood Chatham <roberthoodchatham@gmail.com>
Mon, 3 Apr 2023 02:54:22 +0000 (19:54 -0700)
committerGitHub <noreply@github.com>
Mon, 3 Apr 2023 02:54:22 +0000 (22:54 -0400)
There are three main wasm32 target triples:
* wasm32-unknown-unknown
* wasm32-unknown-emscripten
* wasm32-unknown-wasi

The wasm32 port is only for the wasm32-unknown-emscripten target triple.
(The other triples have no dynamic linking support so libffi would be both
hard to port and of limited utility.)

README.md

index 0f4714b1a72f1a2870fdb82ed429b5ec6ad26113..7029f83b11dcef52127f0e5d69063557e1dce7ad 100644 (file)
--- a/README.md
+++ b/README.md
@@ -100,8 +100,7 @@ tested:
 | SPARC64         | Solaris          | Oracle Solaris Studio C |
 | TILE-Gx/TILEPro | Linux            | GCC                     |
 | VAX             | OpenBSD/vax      | GCC                     |
-| WASM32          | Chrome           | GCC                     |
-| WASM32          | Firefox          | GCC                     |
+| WASM32          | Emscripten       | EMCC                    |
 | X86             | FreeBSD          | GCC                     |
 | X86             | GNU HURD         | GCC                     |
 | X86             | Interix          | GCC                     |