about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorMatthias Krüger <476013+matthiaskrgr@users.noreply.github.com>2025-04-17 21:53:24 +0200
committerGitHub <noreply@github.com>2025-04-17 21:53:24 +0200
commitb6e48d38503a6c25ee55658ff73d6dfe09969f87 (patch)
treea6609f49be339b2d6a9fd1b241120220a00a9306 /compiler/rustc_codegen_llvm/src
parent87a163523f5ecb0aaf6f814d1179ab69f4e5f40b (diff)
parent0da46d1065eb53226211e7dea4ba6103607d6def (diff)
downloadrust-b6e48d38503a6c25ee55658ff73d6dfe09969f87.tar.gz
rust-b6e48d38503a6c25ee55658ff73d6dfe09969f87.zip
Rollup merge of #139483 - RalfJung:nan, r=tgross35
f*::NAN: guarantee that this is a quiet NaN

I think we should guarantee that this is a quiet NaN. This then implies that programs not using `f*::from_bits` (or unsafe type conversions) are guaranteed to only work with quiet NaNs. It would be awkward if people start to write `0.0 / 0.0` instead of using the constant just because they want to get a guaranteed-quiet NaN.

This is a `@rust-lang/libs-api` change. The definition of this constant currently is `0.0 / 0.0`, which is already guaranteed to be a quiet NaN. So all this does is forward that guarantee to our users.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions