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
69 Open 74 Closed
69 Open 74 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

Optimization regression: array argument somehow produces null check? A-ABI Area: Concerning the application binary interface (ABI) A-codegen Area: Code generation C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such I-slow Issue: Problems and improvements with respect to performance of generated code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139415 opened Apr 5, 2025 by alex
5
Tracking issue for wasm32-unknown-unknown's future-incompat warning for C ABI changes A-ABI Area: Concerning the application binary interface (ABI) C-future-incompatibility Category: Future-incompatibility lints C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-wasm Target: WASM (WebAssembly), http://webassembly.org/ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#138762 opened Mar 21, 2025 by alexcrichton
8
ICE: Architecture x86_64 does not support GpuKernel calling convention A-ABI Area: Concerning the application binary interface (ABI) 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_ptx `#![feature(abi_ptx)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#138738 opened Mar 20, 2025 by matthiaskrgr
3
f16 and f128 have non-trivial ABI requirements on some targets A-ABI Area: Concerning the application binary interface (ABI) A-floating-point Area: Floating point numbers and arithmetic C-bug Category: This is a bug. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#138616 opened Mar 17, 2025 by RalfJung
1
Handling of stdcall (and other x86-32-specific ABIs) on non-x86-32 Windows targets is inconsistent A-ABI Area: Concerning the application binary interface (ABI) C-bug Category: This is a bug. I-lang-radar Items that are on lang's radar and will need eventual work or consideration. O-windows Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#137018 opened Feb 14, 2025 by RalfJung
23
Tracking Issue for extern_system_varargs A-ABI Area: Concerning the application binary interface (ABI) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#136946 opened Feb 12, 2025 by workingjubilee
1 of 4 tasks
10
Add a test ensuring all our targets set the features required by their ABI. A-ABI Area: Concerning the application binary interface (ABI) A-testsuite Area: The testsuite used to check the correctness of rustc C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#136208 opened Jan 28, 2025 by RalfJung
4
NaNs are quieted on Emscripten A-ABI Area: Concerning the application binary interface (ABI) A-floating-point Area: Floating point numbers and arithmetic A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-miscompile Issue: Correct Rust code lowers to incorrect machine code O-emscripten Target: 50% off wasm32-unknown-musl. the savings come out of stdio.h, but hey, you get SDL! T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#136197 opened Jan 28, 2025 by purplesyringa
2
Tracking Issue for the gpu-kernel ABI A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-amdgcn Target: the Radeon 9001XT and such O-NVPTX Target: the NVPTX LLVM backend for running rust on GPUs, https://llvm.org/docs/NVPTXUsage.html T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#135467 opened Jan 14, 2025 by Flakebi
1 of 14 tasks
aarch64-unknown-none-softfloat: ABI unsoundness when enabling "neon" feature A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. C-bug Category: This is a bug. I-prioritize Issue: Indicates that prioritization has been requested for this issue. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-AArch64 Armv8-A or later processors in AArch64 mode T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134375 opened Dec 16, 2024 by RalfJung
1
32
Rust's i128 return ABI does not agree with Clang and GCC on Windows targets A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-windows Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134288 opened Dec 13, 2024 by tgross35
1
7
Remove wasm legacy abi A-ABI Area: Concerning the application binary interface (ABI) O-wasm Target: WASM (WebAssembly), http://webassembly.org/ S-blocked Status: Blocked on something else such as an RFC or other implementation work. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133952 opened Dec 6, 2024 by bjorn3 • Draft
4
@alexcrichton @workingjubilee
11
How should we handle dynamic vector ABIs? A-ABI Area: Concerning the application binary interface (ABI) A-SIMD Area: SIMD (Single Instruction Multiple Data) 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-AArch64 Armv8-A or later processors in AArch64 mode O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133146 opened Nov 17, 2024 by workingjubilee
How should we handle matrix ABIs? A-ABI Area: Concerning the application binary interface (ABI) C-discussion Category: Discussion or questions that doesn't represent real issues. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status O-AArch64 Armv8-A or later processors in AArch64 mode O-PowerPC Target: PowerPC processors 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.
#133144 opened Nov 17, 2024 by workingjubilee
5
How should we handle SPARC's vector ABI? A-ABI Area: Concerning the application binary interface (ABI) A-SIMD Area: SIMD (Single Instruction Multiple Data) 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-SPARC Target: SPARC processors T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133141 opened Nov 17, 2024 by workingjubilee
1
Support calling functions with SIMD vectors that couldn't be used in the caller A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-SIMD Area: SIMD (Single Instruction Multiple Data) C-feature-request Category: A feature request, i.e: not implemented / a PR. T-opsem Relevant to the opsem team WG-llvm Working group: LLVM backend code generation
#132865 opened Nov 10, 2024 by RalfJung
2
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
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-*) (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.
#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-*) (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.
#132834 opened Nov 10, 2024 by workingjubilee
Some -Ctarget-features must be restrained on RISCV A-ABI Area: Concerning the application binary interface (ABI) A-floating-point Area: Floating point numbers and arithmetic C-bug Category: This is a bug. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132618 opened Nov 4, 2024 by workingjubilee
20
ICE: internal compiler error[E0391]: cycle detected when computing function signature of impl A-ABI Area: Concerning the application binary interface (ABI) A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. F-cmse_nonsecure_entry `#![feature(cmse_nonsecure_entry)]` I-cycle Issue: A query cycle occurred while none was expected I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132430 opened Oct 31, 2024 by matthiaskrgr
2
abi_unsupported_vector_types lint is optimization-dependent A-ABI Area: Concerning the application binary interface (ABI) A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. 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 L-abi_unsupported_vector_types Lint: abi_unsupported_vector_types T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#132129 opened Oct 25, 2024 by RalfJung
ProTip! Updated in the last three days: updated:>2025-05-14.