-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Tracking Issue for asm_experimental_reg #133416
Copy link
Copy link
Open
Labels
A-inline-assemblyArea: Inline assembly (`asm!(…)`)Area: Inline assembly (`asm!(…)`)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCO-SystemZTarget: SystemZ processors (s390x)Target: SystemZ processors (s390x)O-riscvTarget: RISC-V architectureTarget: RISC-V architectureO-x86_32Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
Metadata
Metadata
Assignees
Labels
A-inline-assemblyArea: Inline assembly (`asm!(…)`)Area: Inline assembly (`asm!(…)`)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCO-SystemZTarget: SystemZ processors (s390x)Target: SystemZ processors (s390x)O-riscvTarget: RISC-V architectureTarget: RISC-V architectureO-x86_32Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)Target: x86 processors, 32 bit (like i686-*) (also known as IA-32, i386, i586, i686)O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
Type
Fields
Give feedbackNo fields configured for issues without a type.
This tracks support for additional registers in architectures where inline assembly is already stable.
The feature gate for the issue is
#![feature(asm_experimental_reg)].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
Implementation history
u128/i128to inline assembly #151059i128to assembly onaarch64#154342Other candidates:
@rustbot label +A-inline-assembly +O-SystemZ +O-riscv +O-x86_32 +O-x86_64