Skip to content

Tracking issue for -Z randomize-layout #106764

Open

Description

@dtolnay

This is a tracking issue for the unstable rustc flag -Zrandomize-layout. (rust-lang/compiler-team#457)

About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved Questions

Implementation history

Activity

  1. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    A-layoutArea: Memory layout of types
    on Jan 12, 2023
  2. saethlin commented on Jan 12, 2023

    @saethlin
  3. added
    A-CLIArea: Command-line interface (CLI) to the compiler
    -Zrandomize-layoutUnstable option: Randomize the layout of types.
    on Mar 5, 2023
  4. added a commit that references this issue on Nov 24, 2024
  5. added a commit that references this issue on Dec 3, 2024
  6. added a commit that references this issue on Dec 3, 2024
  7. added 2 commits that reference this issue on Dec 3, 2024
  8. added a commit that references this issue on Dec 3, 2024
  9. added a commit that references this issue on Jan 10, 2025
  10. added a commit that references this issue on Jan 10, 2025
  11. added a commit that references this issue on Jan 10, 2025
  12. jethrogb commented on Jan 15, 2026

    @jethrogb
    Contributor

    When testing std itself, std is compiled twice: once cfg(not(test)) as a dependency of test and once cfg(test) as the crate-under-test. Are both of these compilations subject to different randomization? See #150131 for further discussion

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

    -Zrandomize-layoutUnstable option: Randomize the layout of types.A-CLIArea: Command-line interface (CLI) to the compilerA-layoutArea: Memory layout of typesC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-impl-incompleteStatus: The implementation is incomplete.S-tracking-needs-documentationStatus: Needs documentation.S-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions