granite-rust/library/core
bors 39b7669347 Auto merge of - RalfJung:float-classify, r=workingjubilee
simplify float::classify logic

I played around with the float-classify test in the hope of triggering x87 bugs by strategically adding `black_box`, and still the exact expression `@beetrees` suggested [here](https://github.com/rust-lang/rust/pull/129835#issuecomment-2325661597) remains the only case I found where we get the wrong result on x87. Curiously, this bug only occurs when MIR optimizations are enabled -- probably the extra inlining that does is required for LLVM to hit the right "bad" case in the backend. But even for that case, it makes no difference whether `classify` is implemented in the simple bit-pattern-based version or the more complicated version we had before.

Without even a single testcase that can distinguish our `classify` from the naive version, I suggest we switch to the naive version.
2024-09-16 03:36:03 +00:00
..
benches Improve isqrt tests and add benchmarks 2024-08-28 23:06:54 -04:00
src Auto merge of - RalfJung:float-classify, r=workingjubilee 2024-09-16 03:36:03 +00:00
tests stabilize const_mut_refs 2024-09-15 09:51:32 +02:00
Cargo.toml Port std library to RTEMS 2024-09-03 09:19:29 +02:00