diff options
| author | Trevor Gross <tmgross@umich.edu> | 2025-06-30 16:53:21 -0500 |
|---|---|---|
| committer | Trevor Gross <tmgross@umich.edu> | 2025-07-02 01:18:54 -0500 |
| commit | be35d37d8b6c206576ff3cdcad956d921b47cc6b (patch) | |
| tree | caf31c698ab2f77edda0fa4be0f290c6fb0ad7df /tests/codegen-llvm/src-hash-algorithm/src-hash-algorithm-md5.rs | |
| parent | 6c4221818e00828ecf54b395475477f49d0ea716 (diff) | |
| download | rust-be35d37d8b6c206576ff3cdcad956d921b47cc6b.tar.gz rust-be35d37d8b6c206576ff3cdcad956d921b47cc6b.zip | |
Use the compiler to determine whether or not to enable `f16` and `f128`
Currently we whether or not to build and test `f16` and `f128` support
mostly based on the target triple. This isn't always accurate, however,
since support also varies by backend and the backend version.
Since recently, `rustc` is aware of this with the unstable config option
`target_has_reliable_{f16,f128}`, which better represents when the types
are actually expected to be available and usable. Switch our
compiler-builtins and libm configuration to use this by probing `rustc`
for the target's settings.
A few small `cfg` fixes are needed with this.
Diffstat (limited to 'tests/codegen-llvm/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions