-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
target abi #86922
target abi #86922
Conversation
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Add an `abi` field to `TargetOptions`, defaulting to "". Support using `cfg(target_abi = "...")` for conditional compilation on that field. Gated by `feature(cfg_target_abi)`. Add a test for `target_abi`, and a test for the feature gate. Add `target_abi` to tidy as a platform-specific cfg. This does not add an abi to any existing target.
All eabi targets have target_abi = "eabi". All eabihf targets have target_abi = "eabihf". armv6_unknown_freebsd and armv7_unknown_freebsd have target_abi = "eabihf". All abi64 targets have target_abi = "abi64". All ilp32 targets have target_abi = "ilp32". All softfloat targets have target_abi = "softfloat". All *-uwp-windows-* targets have target_abi = "uwp". All spe targets have target_abi = "spe". All macabi targets have target_abi = "macabi". aarch64-apple-ios-sim has target_abi = "sim". x86_64-fortanix-unknown-sgx has target_abi = "fortanix". x86_64-unknown-linux-gnux32 has target_abi = "x32". Add FIXME entries for targets for which existing values need to change once cfg_target_abi becomes stable. (All of them are tier 3 targets.) Add a test for target_abi in `--print cfg`.
@bors r+ |
📌 Commit c3fbafd has been approved by |
I know I'm late to the party.
Does that mean that for these targets
This makes me wonder if |
⌛ Testing commit c3fbafd with merge 59740625d3c7cdc653045f4de4b973b2c08128f0... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@nagisa I think it should be 0-or-more, yes. That would take an updated RFC to propose. In the meantime, this is forward-compatible; we can always make |
The test failure appears to be entirely unrelated. |
@bors retry |
☀️ Test successful - checks-actions |
Implement cfg(target_abi) (RFC 2992)
Add an
abi
field toTargetOptions
, defaulting to "". Support usingcfg(target_abi = "...")
for conditional compilation on that field.Gated by
feature(cfg_target_abi)
.Add a test for
target_abi
, and a test for the feature gate.Add
target_abi
to tidy as a platform-specific cfg.Update targets to use
target_abi
All eabi targets have
target_abi = "eabi".
All eabihf targets have
target_abi = "eabihf"
.armv6_unknown_freebsd
andarmv7_unknown_freebsd
havetarget_abi = "eabihf"
.All abi64 targets have
target_abi = "abi64"
.All ilp32 targets have
target_abi = "ilp32"
.All softfloat targets have
target_abi = "softfloat"
.All -uwp-windows- targets have
target_abi = "uwp"
.All spe targets have
target_abi = "spe"
.All macabi targets have
target_abi = "macabi"
.aarch64-apple-ios-sim has
target_abi = "sim"
.x86_64-fortanix-unknown-sgx
hastarget_abi = "fortanix"
.x86_64-unknown-linux-gnux32
hastarget_abi = "x32"
.Add FIXME entries for targets for which existing values need to change
once
cfg_target_abi
becomes stable. (All of them are tier 3 targets.)Add a test for
target_abi
in--print cfg
.