Directly calling "x86-interrupt" fn
should be invalid
#132834
Labels
A-ABI
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.
I tried this code:
I expected to see rustc reject the erroneous code somewhere before final LLVM lowering, because the notion of "calling" an interrupt is nonsensical, no matter what its signature is.
Instead, this happened:
Meta
rustc --version --verbose
:Backtrace
Related Issues
x86-interrupt
calling convention #40180extern "x86-interrupt" fn
allows absurd signatures #132835"msp430-interrupt" fn
should also be invalid #132839()
or!
as return types #132841The text was updated successfully, but these errors were encountered: