rust-lang / rust-lang/rust

Tracking Issue for LoongArch64 SIMD Intrinsics

Open
#162,508 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the LoongArch64 SIMD Intrinsics.
The feature gate for the issue is #![feature(stdarch_loongarch)].
Parent tracking issue: #117427

Public API
core::arch::loongarch64::lsx_*
core::arch::loongarch64::lasx_*
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
  • list all the "unresolved questions" found in the RFC to ensure they are
    not forgotten.
Implementation history

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 the LoongArch64 public API entries and the linked stdarch pull requests (#1535, #1553, #1879, and #2017), using the feature gate stdarch_loongarch as the entry point. Done means the implementation, documentation, style work, and stabilization checklist items are completed.

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
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.