Hi, > have a dynamic branch looking at the CPU feature in the generated assembly.
I would suggest to do this. You can look for instance at `IncsspqIfSupported` in builtins-x64.cc to see how you can retrieve CpuFeatures at runtime from builtins. And another example is the `supports_wasm_simd_128_address` external reference, used on a few architectures. You should be able to do a similar thing with the CodeStubAssembler if needed. Cheers, Darius On Friday, September 5, 2025 at 9:48:15 AM UTC+2 [email protected] wrote: > On RISC-V we need to store vector registers in the builtin > Generate_WasmCompileLazy (and others). However, not all CPUs have vector > support. It's dynamically detected, and then used accordingly. > Given that the builtins are precompiled, we can't use > `CpuFeatures::IsSupported` as that wouldn't take the actual hardware into > account. > We would either remove these functions from precompilation, or have a > dynamic branch looking at the CPU feature in the generated assembly. > > Did other architectures run into similar issues? > Any suggestions on how to handle this? > > Thanks. > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/ab08ef07-af9e-43f0-adeb-a59587e30e40n%40googlegroups.com.
