build: use clang instead of llvm-gcc (#300)

Modern clang works just fine, also llvm-gcc is nowhere to be found.
This commit is contained in:
ryan-filmware
2024-04-02 22:31:00 -06:00
committed by GitHub
parent b42f035afb
commit b3a6e991a4
2 changed files with 2 additions and 1 deletions
+1
View File
@@ -39,6 +39,7 @@ endif
ifeq ($(ARCH),wasm32) ifeq ($(ARCH),wasm32)
USECLANG = 1 USECLANG = 1
USEGCC = 0
TOOLPREFIX = llvm- TOOLPREFIX = llvm-
endif endif
+1 -1
View File
@@ -29,7 +29,7 @@ loongarch64.
Linux and Windows. Linux and Windows.
3. Use `make USECLANG=1` to build with clang. This is the default on OS X, FreeBSD, 3. Use `make USECLANG=1` to build with clang. This is the default on OS X, FreeBSD,
and OpenBSD. and OpenBSD.
4. Use `make ARCH=wasm32` to build the wasm32 library with clang. Requires clang-8. 4. Use `make ARCH=wasm32` to build the wasm32 library with clang.
5. Architectures are auto-detected. Use `make ARCH=i386` to force a 5. Architectures are auto-detected. Use `make ARCH=i386` to force a
build for i386. Other supported architectures are i486, i586, and build for i386. Other supported architectures are i486, i586, and
i686. GCC 4.8 is the minimum requirement for correct codegen on i686. GCC 4.8 is the minimum requirement for correct codegen on