You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, a current blocker is to make sure that this will not cause any performance regression on any target. Part of this involves knowing what LLVM will do on the less common CPU types, so I'm coming to you because I hope you know, or know how to find out.
Intel, ARM, Wasm32: all fine
Mips, PowerPC, Risc-V: ???
In Brief: Ideally we'd like core::intrinsics::sqrtf32() to generate a hardware instruction if that CPU supports that, and of it doesn't have a hardware instruction we want to male sure that the software sqrt in the libm crate (exposed on some targets via compiler-builtins) is either at least as fast as the system libm library or doesn't get exposed on that target so that the system libm gets used.
This is where yall come in. Hopefully you folks have ways to check the builds on those targets and ways to check the system libm and run benchmarks and so on. Or you know people who do perhaps.
The text was updated successfully, but these errors were encountered:
Heya folks,
As part of the 2019 Embedded-wg Wishlist I've opened a PR to move
sqrt
fromstd
intocore
:rust-lang/rust#63455
However, a current blocker is to make sure that this will not cause any performance regression on any target. Part of this involves knowing what LLVM will do on the less common CPU types, so I'm coming to you because I hope you know, or know how to find out.
In Brief: Ideally we'd like
core::intrinsics::sqrtf32()
to generate a hardware instruction if that CPU supports that, and of it doesn't have a hardware instruction we want to male sure that the softwaresqrt
in thelibm
crate (exposed on some targets viacompiler-builtins
) is either at least as fast as the system libm library or doesn't get exposed on that target so that the system libm gets used.This is where yall come in. Hopefully you folks have ways to check the builds on those targets and ways to check the system libm and run benchmarks and so on. Or you know people who do perhaps.
The text was updated successfully, but these errors were encountered: