summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorJubilee <workingjubilee@gmail.com>2024-11-13 22:43:35 -0800
committerGitHub <noreply@github.com>2024-11-13 22:43:35 -0800
commit52913653ddd823fbd67f5cd3f1d48ef882ff8276 (patch)
tree8bbceadd4ce7558566a164901b1f0f92dcde6ab2 /tests/rustdoc-js-std/parser-errors.js
parentbd0826a4521a845f36cce1b00e1dd2918ba09e90 (diff)
parent2d3c08a02216693f26b5a8c3c44bb8a6be8abc0b (diff)
downloadrust-52913653ddd823fbd67f5cd3f1d48ef882ff8276.tar.gz
rust-52913653ddd823fbd67f5cd3f1d48ef882ff8276.zip
Rollup merge of #131304 - RalfJung:float-core, r=tgross35
float types: move copysign, abs, signum to libcore

These operations are explicitly specified to act "bitwise", i.e. they just act on the sign bit and do not even quiet signaling NaNs. We also list them as ["non-arithmetic operations"](https://doc.rust-lang.org/nightly/std/primitive.f32.html#nan-bit-patterns), and all the other non-arithmetic operations are in libcore. There's no reason to expect them to require any sort of runtime support, and from [these experiments](https://github.com/rust-lang/rust/issues/50145#issuecomment-997301250) it seems like LLVM indeed compiles them in a way that does not require any sort of runtime support.

Nominating for `@rust-lang/libs-api` since this change takes immediate effect on stable.

Part of https://github.com/rust-lang/rust/issues/50145.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions