Tracking Issue for sparc_target_feature #132783
Labels
A-target-feature
Area: Enabling/disabling target features like AVX, Neon, etc.
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
O-SPARC
Target: SPARC processors
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
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))v8plus
target feature withoutv9
target feature should be rejected. (AFAIK, there is no existing mechanism to represent this.)rust/tests/ui/abi/sparcv8plus.rs
Lines 37 to 39 in c059eb7
Or, enable
v9
target feature automatically whenv8plus
target feature enabled.Implementation history
v9
,v8plus
,leoncasa
: Add v9, v8plus, and leoncasa target feature to sparc and use v8plus in create_object_file #132552@rustbot label +O-SPARC +A-target-feature
The text was updated successfully, but these errors were encountered: