Skip to content

Tracking Issue for target-spec-json (flexible target specifications) #151528

@ehuss

Description

@ehuss

This is a tracking issue for the RFC "Flexible target specification" (rust-lang/rfcs#131).

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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Overview

This is the tracking issue for the ability to specify custom targets using a file that defines the target (currently JSON).
See also #38338 for the related --print=target-spec-json.

Documentation: https://doc.rust-lang.org/nightly/rustc/targets/custom.html
Issues: A-target-specs Area: Compile-target specifications

Unresolved Questions

  • Should the file format be JSON or something else like TOML?
  • The format is somewhat tied to LLVM. There are some concerns that may make using other backends more difficult. Here is a suggestion for making the backend explicit.
  • How will stability be handled?
  • Validate that the standard library can be reliably built (no TARGET detection, see Target specification? wg-cargo-std-aware#6 (comment)).

Implementation history

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-target-specsArea: Compile-target specificationsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-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