about summary refs log tree commit diff
path: root/tests/rustdoc-js/slice-array.js
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-11-19 18:42:20 +0000
committerbors <bors@rust-lang.org>2023-11-19 18:42:20 +0000
commitd19980e1ce9cde530240ed9d42ab54bb79ce8b40 (patch)
tree4c1ad0b8246d11591ffce106c91e039a32322a02 /tests/rustdoc-js/slice-array.js
parent290fc68f2d27b67da5fd176965c42c01ea4c57fe (diff)
parentc7b8dd4e93ff1fa5e2136cdd43e1e563ae45f3b8 (diff)
downloadrust-d19980e1ce9cde530240ed9d42ab54bb79ce8b40.tar.gz
rust-d19980e1ce9cde530240ed9d42ab54bb79ce8b40.zip
Auto merge of #117500 - RalfJung:aggregate-abi, r=davidtwco
Ensure sanity of all computed ABIs

This moves the ABI sanity assertions from the codegen backend to the ABI computation logic. Sadly, due to past mistakes, we [have to](https://github.com/rust-lang/rust/pull/117351#issuecomment-1788495503) be able to compute a sane ABI for nonsensical function types like `extern "C" fn(str) -> str`.  So to make the sanity check pass we first need to make all ABI adjustment deal with unsized types... and we have no shared infrastructure for those adjustments, so that's a bunch of copy-paste. At least we have assertions failing loudly when one accidentally sets a different mode for an unsized argument.

To achieve this, this re-lands the parts of https://github.com/rust-lang/rust/pull/80594 that got reverted in https://github.com/rust-lang/rust/pull/81388.  To avoid breaking wasm ABI again, that ABI now explicitly opts-in to the (wrong, broken) ABI that we currently keep for backwards compatibility. That's still better than having *every* ABI use the wrong broken default!

Cc `@bjorn3`
Fixes https://github.com/rust-lang/rust/issues/115845
Diffstat (limited to 'tests/rustdoc-js/slice-array.js')
0 files changed, 0 insertions, 0 deletions