-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Issues: rust-lang/rust
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Error: "offset is not a multiple of ??"
A-diagnostics
Area: Messages for errors, warnings, and lints
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
C-bug
Category: This is a bug.
F-abi_x86_interrupt
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#139679
opened Apr 11, 2025 by
ViktorPopp
All interrupt ABIs should enforce either Area: Concerning the application binary interface (ABI)
A-hardware-interrupts
Area: Code for handling the "interrupt ABI" of various processors
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
C-bug
Category: This is a bug.
F-abi_x86_interrupt
O-msp430
O-riscv
Target: RISC-V architecture
O-x86_32
Target: x86 processors, 32 bit (like i686-*) (IA-32)
O-x86_64
Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
()
or !
as return types
A-ABI
#132841
opened Nov 10, 2024 by
workingjubilee
extern "x86-interrupt" fn
allows absurd signatures
A-ABI
#132835
opened Nov 10, 2024 by
workingjubilee
Directly calling Area: Concerning the application binary interface (ABI)
A-hardware-interrupts
Area: Code for handling the "interrupt ABI" of various processors
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
C-bug
Category: This is a bug.
F-abi_x86_interrupt
O-x86_32
Target: x86 processors, 32 bit (like i686-*) (IA-32)
O-x86_64
Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
"x86-interrupt" fn
should be invalid
A-ABI
#132834
opened Nov 10, 2024 by
workingjubilee
ICE: Area: Code for handling the "interrupt ABI" of various processors
C-bug
Category: This is a bug.
F-abi_x86_interrupt
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Tried to make Ignore indirect
A-hardware-interrupts
#126418
opened Jun 13, 2024 by
matthiaskrgr
ICE: Area: Code for handling the "interrupt ABI" of various processors
C-bug
Category: This is a bug.
F-abi_x86_interrupt
F-unsized_fn_params
`#![feature(unsized_fn_params)]`
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
used byval ABI for unsized layout
A-hardware-interrupts
#124806
opened May 6, 2024 by
matthiaskrgr
SIGSEGV during compilation of extern x86-interrupt fn with u128 param
A-hardware-interrupts
Area: Code for handling the "interrupt ABI" of various processors
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
C-bug
Category: This is a bug.
F-abi_x86_interrupt
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
O-x86_32
Target: x86 processors, 32 bit (like i686-*) (IA-32)
O-x86_64
Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
requires-nightly
This issue requires a nightly compiler in some way.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
#63018
opened Jul 26, 2019 by
bjorn3
Tracking issue for the Area: Code for handling the "interrupt ABI" of various processors
B-unstable
Blocker: Implemented in the nightly compiler and unstable.
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
F-abi_x86_interrupt
S-tracking-needs-summary
Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
x86-interrupt
calling convention
A-hardware-interrupts
#40180
opened Mar 1, 2017 by
phil-opp
4 of 13 tasks
ProTip!
Find all open issues with in progress development work with linked:pr.