rust-lang / rust-lang/rust

Tracking Issue for m68k_target_feature

Open
#134,328 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-target-feature C-tracking-issue O-motorola68k
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for M68k architecture specific part of https://github.com/rust-lang/rust/issues/44839 (RFC 2045 (rust-lang/rfcs#2045)).
The feature gate for the issue is #![feature(m68k_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
  • isa-68000 is baseline of this architecture, so it may not actually need to be expressed as a target feature.
Implementation history

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with RFC 2045, the implementation PR #134329, and the rustc-dev-guide stabilization instructions. Review the unresolved question about whether isa-68000 should be expressed as a target feature. Done means completing the stabilization PR and updating the tracking checklist.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.