Skip to content

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
13 Open 0 Closed
13 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

All interrupt ABIs should enforce either () or ! as return types 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-msp430 O-riscv Target: RISC-V architecture O-x86_32 Target: x86 processors, 32 bit (like i686-*) O-x86_64 Target: x86-64 processors (like x86_64-*) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132841 opened Nov 10, 2024 by workingjubilee
Directly calling "msp430-interrupt" fn should also be invalid 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. O-msp430 T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132839 opened Nov 10, 2024 by workingjubilee
Most extern "*-interrupt-*" fn should enforce 0-sized signatures 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. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-msp430 O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132837 opened Nov 10, 2024 by workingjubilee
3
Directly calling extern "riscv-interrupt-{m,s}" fn... compiles? 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. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132836 opened Nov 10, 2024 by workingjubilee
6
extern "x86-interrupt" fn allows absurd signatures 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-*) O-x86_64 Target: x86-64 processors (like x86_64-*) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132835 opened Nov 10, 2024 by workingjubilee
Directly calling "x86-interrupt" fn should be invalid 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-*) O-x86_64 Target: x86-64 processors (like x86_64-*) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132834 opened Nov 10, 2024 by workingjubilee
ICE: Tried to make Ignore indirect A-hardware-interrupts 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.
#126418 opened Jun 13, 2024 by matthiaskrgr
2
ICE: used byval ABI for unsized layout A-hardware-interrupts 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.
#124806 opened May 6, 2024 by matthiaskrgr
@JoverZhang
3
Tracking Issue for riscv-interrupt-{m,s} ABIs A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#111889 opened May 23, 2023 by sethp
1 of 3 tasks
1
Tracking Issue for the avr-interrupt/avr-non-blocking-interrupt calling convention/ABI A-hardware-interrupts 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 O-AVR Target: AVR processors (ATtiny, ATmega, etc.) 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. WG-embedded Working group: Embedded systems
#69664 opened Mar 3, 2020 by dylanmckay
1 of 3 tasks
2
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-*) O-x86_64 Target: x86-64 processors (like x86_64-*) 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
4
Tracking issue for the x86-interrupt calling convention A-hardware-interrupts 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.
#40180 opened Mar 1, 2017 by phil-opp
4 of 13 tasks
37
Tracking issue for the msp430-interrupt calling convention/ABI A-hardware-interrupts 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 O-msp430 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. WG-embedded Working group: Embedded systems
#38487 opened Dec 20, 2016 by japaric
5
ProTip! Exclude everything labeled bug with -label:bug.