You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On `s390x` targets, use of functions with the `#[target_feature]` attribute follows the [above restrictions][attributes.codegen.target_feature.safety-restrictions].
585
+
586
+
Further documentation on these features can be found in the "Additions to z/Architecture" section of Chapter 1 of the *[z/Architecture Principles of Operation]*.
[z/Architecture Principles of Operation]: https://publibfp.dhe.ibm.com/epubs/pdf/a227832d.pdf
604
+
581
605
r[attributes.codegen.target_feature.info]
582
606
### Additional information
583
607
@@ -588,8 +612,7 @@ that this option is not affected by the `target_feature` attribute, and is
588
612
only driven by the features enabled for the entire crate.
589
613
590
614
r[attributes.codegen.target_feature.remark-rt]
591
-
See the [`is_x86_feature_detected`] or [`is_aarch64_feature_detected`] macros
592
-
in the standard library for runtime feature detection on these platforms.
615
+
Whether a feature is enabled can be checked at runtime using a platform-specific macro from the standard library, for instance [`is_x86_feature_detected`] or [`is_aarch64_feature_detected`].
593
616
594
617
> [!NOTE]
595
618
> `rustc` has a default set of features enabled for each target and CPU. The CPU may be chosen with the [`-C target-cpu`] flag. Individual features may be enabled or disabled for an entire crate with the [`-C target-feature`] flag.
0 commit comments