diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-03 21:53:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-03 21:53:36 +0200 |
| commit | 644f06ec1fd8b17de40d42c699a61020db02a123 (patch) | |
| tree | 25c8aa492416b29c06ffbf29977bc19622b50204 /compiler/rustc_codegen_llvm/src/mono_item.rs | |
| parent | d096ebf8d93e78b429c5c5866ecc60b3a5d9ed18 (diff) | |
| parent | 307a18dc537fa3f5ee406f0d21c60c26bea18ec8 (diff) | |
| download | rust-644f06ec1fd8b17de40d42c699a61020db02a123.tar.gz rust-644f06ec1fd8b17de40d42c699a61020db02a123.zip | |
Rollup merge of #141569 - workingjubilee:canonicalize-abi, r=bjorn3
Replace ad-hoc ABI "adjustments" with an `AbiMap` to `CanonAbi`
Our `conv_from_spec_abi`, `adjust_abi`, and `is_abi_supported` combine to give us a very confusing way of reasoning about what _actual_ calling convention we want to lower our code to and whether we want to compile the resulting code at all. Instead of leaving this code as a miniature adventure game in which someone tries to combine stateful mutations into a Rube Goldberg machine that will let them escape the maze and arrive at the promised land of codegen, we let `AbiMap` devour this complexity. Once you have an `AbiMap`, you can answer which `ExternAbi`s will lower to what `CanonAbi`s (and whether they will lower at all).
Removed:
- `conv_from_spec_abi` replaced by `AbiMap::canonize_abi`
- `adjust_abi` replaced by same
- `Conv::PreserveAll` as unused
- `Conv::Cold` as unused
- `enum Conv` replaced by `enum CanonAbi`
target-spec.json changes:
- If you have a target-spec.json then now your "entry-abi" key will be specified in terms of one of the `"{abi}"` strings Rust recognizes, e.g.
```json
"entry-abi": "C",
"entry-abi": "win64",
"entry-abi": "aapcs",
```
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/mono_item.rs')
0 files changed, 0 insertions, 0 deletions