compiler-team icon indicating copy to clipboard operation
compiler-team copied to clipboard

Rename `hexagon-unknown-{none-elf,linux-musl}` targets

Open androm3da opened this issue 3 months ago • 2 comments

Rename hexagon-unknown-{none-elf,linux-musl} targets

  • Rename hexagon-unknown-linux-musl target to hexagon-linux-musl
  • Rename hexagon-unknown-none-elf target to hexagon-none-elf

Rationale

Let's simplify the target name by omitting the implied vendor element. If one or both targets above become vendored targets, those ones must explicitly name the vendor and the vendored target must be added (or it should replace the un-vendored target, if appropriate).

These tier 3 targets see somewhat narrow Rust use so far and it makes sense to change the names now before we take effort to promote them to higher tiers.

Mentors or Reviewers

@tgross35 might make a good mentor/reviewer.

Process

The main points of the Major Change Process are as follows:

  • [x] File an issue describing the proposal.
  • [ ] A compiler team member who is knowledgeable in the area can second by writing @rustbot second or kickoff a team FCP with @rfcbot fcp $RESOLUTION.
  • [ ] Once an MCP is seconded, the Final Comment Period begins.
    • Final Comment Period lasts for 10 days after all outstanding concerns are solved.
    • Outstanding concerns will block the Final Comment Period from finishing. Once all concerns are resolved, the 10 day countdown is restarted.
    • If no concerns are raised after 10 days since the resolution of the last outstanding concern, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

androm3da avatar Oct 03 '25 01:10 androm3da

[!IMPORTANT] This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Concerns or objections can formally be registered here by adding a comment.

@rustbot concern reason-for-concern
<description of the concern>

Concerns can be lifted with:

@rustbot resolve reason-for-concern

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

rustbot avatar Oct 03 '25 01:10 rustbot

cc @crsabotta

androm3da avatar Oct 03 '25 01:10 androm3da