-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Bump autocfg to 1.1.0 #94494
Bump autocfg to 1.1.0 #94494
Conversation
autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup=iffy |
📌 Commit b83a48d has been approved by |
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
☀️ Test successful - checks-actions |
Finished benchmarking commit (9fcbc32): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
autocfg 1.1.0 makes it so that rustflags from the build are correctly
passed to the compiler probes, which in turn means those probes more
accurately reflect the outer build conditions. This is particularly
important if rustflags includes required
-Clink-arg=
flags withoutwhich builds will fail, as older versions of
autocfg
will then failthe probe and erroneously report the probed feature as unavailable.
See also
#94007 (comment)