<!-- NOTE: For library features, please use the "Library Tracking Issue" template instead. Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a feature from implementation to stabilisation. Make sure to include the relevant RFC for the feature if it has one. Otherwise provide a short summary of the feature and link any relevant PRs or issues, and remove any sections that are not relevant to the feature. Remember to add team labels to the tracking issue. For a language team feature, this would e.g., be `T-lang`. Such a feature should also be labeled with e.g., `F-my_feature`. This label is used to associate issues (e.g., bugs and design questions) to the feature. --> This is a tracking issue for the `xtensa_target_feature` feature The feature gate for the issue is `#![feature(xtensa_target_feature)]`. ### Steps ### Unresolved Questions <!-- Include any open questions that need to be answered before the feature can be stabilised. It is useful to link related discussions and conculsions as they develop. --> ### Implementation history - https://github.com/rust-lang/rust/pull/125141 - https://github.com/rust-lang/rust/pull/133599 - https://github.com/rust-lang/rust/pull/127565 - https://github.com/rust-lang/rust/pull/147300 - https://github.com/rust-lang/rust/pull/140253
This is a tracking issue for the
xtensa_target_featurefeatureThe feature gate for the issue is
#![feature(xtensa_target_feature)].Steps
Unresolved Questions
Implementation history
+forced-atomicsfeature to esp32s2 no_std target #133599