about summary refs log tree commit diff
path: root/tests/ui/rfcs
diff options
context:
space:
mode:
authorJacob Pratt <jacob@jhpratt.dev>2025-07-26 22:42:34 -0400
committerGitHub <noreply@github.com>2025-07-26 22:42:34 -0400
commit2c395c77597e81b0f2058410427dd03970b6d7f8 (patch)
tree20544c1b81d0ff0afb39a40e17bf2c4a6ab2ae9f /tests/ui/rfcs
parentc96c80250e39412f480bca0e9ea2121252d08ac5 (diff)
parent732097ea61c9282a82d8b5fe8d5e8b00c6ac8ccd (diff)
downloadrust-2c395c77597e81b0f2058410427dd03970b6d7f8.tar.gz
rust-2c395c77597e81b0f2058410427dd03970b6d7f8.zip
Rollup merge of #144383 - ZuseZ4:disable-f128-on-amdgcn, r=oli-obk
disable cfg.has_reliable_f128 on amdgcn

I was experimenting with compiling a few kernels for amd while working on std::offload. It seems like the logic in https://github.com/rust-lang/compiler-builtins/pull/737 got removed, so I re-introduce it here. Probably should have a test to avoid another regression and make sure that f128 doesn't show up as target feature for amdgcn. It looks like currently we neither check that for nvptx, nor amdgpu. Maybe I could add two revisions to https://github.com/rust-lang/rust/blob/master/tests/ui/float/target-has-reliable-nightly-float.rs?
r? ````@Flakebi````

fixes: https://github.com/rust-lang/rust/issues/144381
Diffstat (limited to 'tests/ui/rfcs')
0 files changed, 0 insertions, 0 deletions