Skip to content

Issues: rust-lang/rust

Draft release notes for 1.88.0
#141598 opened May 26, 2025 by Mark-Simulacrum
Open 9
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
8 Open 9 Closed
8 Open 9 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
Assigned to nobody Loading
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-*) (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.
#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
The __mspabi_fltlif implementation of MSP430 seems to be wrong? O-msp430
#109210 opened Mar 16, 2023 by 823984418
Consider simulation testing for math on 16-bit targets A-testsuite Area: The testsuite used to check the correctness of rustc C-discussion Category: Discussion or questions that doesn't represent real issues. E-needs-design This issue needs exploration and design to see how and if we can fix/implement it O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-msp430
#107612 opened Feb 2, 2023 by workingjubilee
8
Inlined function duplication across complex branches when extern "Rust" is used with LTO and opt-level="s" A-LTO Area: Link-time optimization (LTO) C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such I-heavy Issue: Problems and improvements with respect to binary size of generated code. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-msp430 T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#102295 opened Sep 26, 2022 by cr1901
Can't compile core for msp430 - LLVM ERROR A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-target-specs Area: Compile-target specifications C-bug Category: This is a bug. O-msp430 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. WG-embedded Working group: Embedded systems
#45835 opened Nov 7, 2017 by japaric
2
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! Type g i on any issue or pull request to go back to the issue listing page.