Skip to content

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

@androm3da

Description

@androm3da

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:

  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-compilerAdd this label so rfcbot knows to poll the compiler teammajor-changeA proposal to make a major change to rustcto-announceAnnounce this issue on triage meeting

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions