Skip to content

Tracking Issue for sparc_target_feature #132783

Open
@taiki-e

Description

@taiki-e

This is a tracking issue for SPARC architecture specific part of #44839 (RFC 2045 (rust-lang/rfcs#2045)).
The feature gate for the issue is #![feature(sparc_target_feature)].

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.

Steps

Unresolved Questions

  • Behavior of v8plus target feature is LLVM version dependent until LLVM 20 becomes minimal LLVM version (Our 32-bit Sparc handling isn't quite correct yet #132585 (comment))
  • Enabling v8plus target feature without v9 target feature should be rejected. (AFAIK, there is no existing mechanism to represent this.)
    // FIXME: should be rejected
    #[cfg(all(target_feature = "v8plus", not(target_feature = "v9")))]
    compile_error!("+v8plus,-v9 (FIXME)");

    Or, enable v9 target feature automatically when v8plus target feature enabled.

Implementation history


@rustbot label +O-SPARC +A-target-feature

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-target-featureArea: Enabling/disabling target features like AVX, Neon, etc.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCO-SPARCTarget: SPARC processors

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions