aboutsummaryrefslogtreecommitdiff
path: root/src/target.zig
diff options
context:
space:
mode:
authorLuuk de Gram <luuk@degram.dev>2023-06-18 18:22:04 +0200
committerLuuk de Gram <luuk@degram.dev>2023-06-26 20:00:57 +0200
commit062eb6f3c0027e8a371e6865963645b70e49b84e (patch)
tree8d4acf43c95e976b733a5acddc477ec604c0759d /src/target.zig
parent381937116326400c1162a710c16496152b542443 (diff)
downloadzig-062eb6f3c0027e8a371e6865963645b70e49b84e.tar.gz
zig-062eb6f3c0027e8a371e6865963645b70e49b84e.zip
Compilation: allow threads for Wasm when shared-memory is enabled
When the user enabled the linker-feature 'shared-memory' we do not force a singlethreaded build. The linker already verifies all other CPU features required for threads are enabled. This is true for both WASI and freestanding.
Diffstat (limited to 'src/target.zig')
-rw-r--r--src/target.zig4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/target.zig b/src/target.zig
index 2d27869cf6..28833428a7 100644
--- a/src/target.zig
+++ b/src/target.zig
@@ -207,10 +207,6 @@ pub fn supports_fpic(target: std.Target) bool {
return target.os.tag != .windows and target.os.tag != .uefi;
}
-pub fn isSingleThreaded(target: std.Target) bool {
- return target.isWasm();
-}
-
/// Valgrind supports more, but Zig does not support them yet.
pub fn hasValgrindSupport(target: std.Target) bool {
switch (target.cpu.arch) {