@@ -390,13 +390,6 @@ You can detect and influence the set of supported targets:
390390 order to test each supported target. Calling with ` b == 0 ` restores the
391391 normal ` SupportedTargets ` behavior.
392392
393- ** Note on ` HWY_ARCH_WASM ` ** . The target is automatically detected and enabled;
394- compiler flags such as -msimd128 are not required. This auto-detection
395- behavior is consistent with other architectures (e.g., AVX2, NEON).
396- Developers wishing to disable the ` HWY_ARCH_WASM ` target (e.g., to increase
397- browser compatibility, or workaround compiler bugs) should use the
398- ` HWY_DISABLED_TARGETS ` macro.
399-
400393## Operations
401394
402395In the following, the argument or return type ` V ` denotes a vector with ` N `
@@ -2924,13 +2917,6 @@ binary will likely crash. This can only happen if:
29242917 also not supported by the current CPU, and baseline targets (in particular
29252918 `HWY_SCALAR`) were explicitly disabled.
29262919
2927- **Note on WebAssembly:**: The browser validates the WebAssembly module during
2928- instantiation when using `WebAssembly.instantiate` APIs. If SIMD features are
2929- unsupported, the entire module is rejected. Therefore, dynamic dispatch between
2930- targets (such as `HWY_SCALAR` and `HWY_WASM`) based on runtime feature detection
2931- is not feasible, unlike with native targets. Developers should configure the
2932- `HWY_ARCH_WASM` target at compile time using the `HWY_DISABLED_TARGETS` macro.
2933-
29342920## Advanced configuration macros
29352921
29362922The following macros govern which targets to generate. Unless specified
0 commit comments