Skip to content

Tracking Issue for cfg_target_has_atomic_equal_alignment #93822

Closed

Description

@Amanieu

This is a tracking issue for the target_has_atomic_equal_alignment CFG flag which was added in #76965 for Atomic*::from_mut.

It indicates whether an AtomicX has the same alignment as the equivalent X integer type. On some 32-bit platforms (e.g. x86) AtomicI64 has an alignment of 8 while i64 is only aligned to 4 bytes.


Potential design concerns:

  • Open question of whether a dedicated cfg is necessary over cfg(accessible) on the from_mut method specifically, which is what is currently gated on this cfg

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Feb 9, 2022
  2. added a commit that references this issue on Feb 10, 2022
  3. WaffleLapkin commented on Apr 6, 2026

    @WaffleLapkin
    Member

    T-lang nomination

    I would like to suggest stabilizing this feature.

    It is currently blocking stabilization of atomic_from_mut feature (Atomic*::{from_mut, from_mut_slice, get_mut_slice}), as from_mut and from_mut_slice use this cfg and users would need to gate their uses on the same cfg.

    Open question of whether a dedicated cfg is necessary over cfg(accessible) on the from_mut method specifically, which is what is currently gated on this cfg

    It appears cfg(accessible) is still nowhere near to being stable and I don't see the reason to block this on it.

  4. added
    I-lang-nominatedNominated for discussion during a lang team meeting.
    I-lang-easy-decisionIssue: The decision needed by the team is conjectured to be easy; this does not imply nomination
    on Apr 6, 2026
  5. added
    P-lang-drag-1Lang team prioritization drag level 1. https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang
    on Apr 8, 2026
  6. joshtriplett commented on Apr 8, 2026

    @joshtriplett
    Member

    @WaffleLapkin We discussed this in today's @rust-lang/lang meeting.

    Please do post a stabilization PR for this, and we'll FCP it.

  7. added
    I-lang-radarItems that are on lang's radar and will need eventual work or consideration.
    and removed
    I-lang-nominatedNominated for discussion during a lang team meeting.
    I-lang-easy-decisionIssue: The decision needed by the team is conjectured to be easy; this does not imply nomination
    P-lang-drag-1Lang team prioritization drag level 1. https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang
    on Apr 9, 2026
  8. added a commit that references this issue on May 18, 2026
  9. added a commit that references this issue on May 18, 2026
  10. Mark-Simulacrum commented on Jun 16, 2026

    @Mark-Simulacrum
    Member

    Closing as this is stabilized (in #155006) and documented in the reference (rust-lang/reference#2273). I don't think there's anything further to do here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCI-lang-radarItems that are on lang's radar and will need eventual work or consideration.S-tracking-design-concernsStatus: There are blocking design concerns.S-tracking-needs-to-bakeStatus: The implementation is "complete" but it needs time to bake.T-langRelevant to the language team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions