Tracking issue for MCP 928: Move annotation for profiling compiler-generated moves and copies.

[rustbot]

This is a tracking issue for MCP "Move annotation for profiling compiler-generated moves and copies." (rust-lang/compiler-team#928).

Note

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.
Instead, open a dedicated issue for the specific matter, link to this tracking issue and ping the MCP author.
Alternatively, post in the Zulip stream linked from the MCP.

Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

• Implement the MCP
• Adjust documentation
  • In the Rust Compiler Development Guide if applicable (e.g., for refactorings)
  • In the Rust Forge if applicable (e.g., for policy changes)
  • In the rustc book if applicable (e.g., for target tier or CLI changes)

Unresolved questions

None so far.

Implementation history

• Implement profiling for compiler-generated move/copy operations (MIR transform) #147206
• Add -Zannotate-moves for profiler visibility of move/copy operations (codegen) #147803

[nikunj-kohli]

I would like to contribute here, I request you to assign me

[jsgf]

Implementation PR #147803

[jsgf]

Open question:

• Should the new core::profiling module also be visible as std::profiling, even though it doesn't present any callable APIs?