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
72 Open 1,258 Closed
72 Open 1,258 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

GVN makes an incorrect index access A-mir-opt Area: MIR optimizations A-mir-opt-GVN Area: MIR opt Global Value Numbering (GVN) A-rustlantis A miscompilation found by Rustlantis C-bug Category: This is a bug. I-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141251 opened May 19, 2025 by dianqk
1
@dianqk
copied().min() performance regression on nightly C-bug Category: This is a bug. I-slow Issue: Problems and improvements with respect to performance of generated code. P-high High priority regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#140207 opened Apr 23, 2025 by DaniPopes
6
A case of compound x86_64 performance regression caused by LLVM 20 and #124810 A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such P-high High priority regression-untriaged Untriaged performance or correctness regression. 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.
#139730 opened Apr 13, 2025 by MoSal
3
Performance regression in nightly with target-cpu=native on znver4 A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139370 opened Apr 4, 2025 by nsarlin-zama
25
Panic-safety issue with Zip specializations A-iterators Area: Iterators A-specialization Area: Trait impl specialization C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority T-libs Relevant to the library team, which will review and decide on the PR/issue.
#137255 opened Feb 19, 2025 by steffahn
1
@the8472
2
Hang after encountering overflow errors for huge types A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. I-hang Issue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc. P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. 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.
#132673 opened Nov 6, 2024 by wxie7
1 of 4 tasks
@compiler-errors
9
Regression: geoarrow crate does not compile in release mode on 1.82 A-mir-opt-inlining Area: MIR inlining C-bug Category: This is a bug. P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-types Relevant to the types team, which will review and decide on the PR/issue. WG-mir-opt Working group: MIR optimizations
#131960 opened Oct 20, 2024 by theemathas
8
Implementation of trait "not general enough" in nightly, works fine on stable C-bug Category: This is a bug. P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-types Relevant to the types team, which will review and decide on the PR/issue.
#131488 opened Oct 10, 2024 by ejmount
10
Invalid metadata for arm64e due to Xcode 15+ on ARM64e macOS C-bug Category: This is a bug. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-macos Operating system: macOS P-high High priority regression-untriaged Untriaged performance or correctness regression. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#130834 opened Sep 25, 2024 by arttet
4
unreachable!("state is never set to invalid values") is reached A-linkage Area: linking into static, shared libraries and binaries C-bug Category: This is a bug. C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-windows Operating system: Windows P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. 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.
#127979 opened Jul 19, 2024 by janhohenheim
53
Wasm32 miscompilation when using u128 with multivalue and optimizations A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-external-bug Category: issue that is caused by bugs in software beyond our control I-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-wasm Target: WASM (WebAssembly), http://webassembly.org/ P-high High priority 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.
#127318 opened Jul 4, 2024 by arriven
7
Undefined behavior from stack overflow on wasm32 targets C-bug Category: This is a bug. E-needs-design This issue needs exploration and design to see how and if we can fix/implement it I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-wasm Target: WASM (WebAssembly), http://webassembly.org/ P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#126747 opened Jun 20, 2024 by adambratschikaye
5
-C target_cpu=cortex-a72 (and -target-cpu=native on Raspberry Pi) wrongly enables crypto features that are optional on Cortex-A72 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. A-targets Area: Concerning the implications of different compiler targets C-bug Category: This is a bug. I-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness llvm-fixed-upstream Issue expected to be fixed by the next major LLVM upgrade, or backported fixes O-AArch64 Armv8-A or later processors in AArch64 mode P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125033 opened May 12, 2024 by briansmith
26
RUST_BACKTRACE=full loop with -Cpanic=abort on aarch64-unknown-linux-gnu A-backtrace Area: Backtraces A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-bug Category: This is a bug. O-AArch64 Armv8-A or later processors in AArch64 mode P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#123733 opened Apr 10, 2024 by cuviper
1
25
f64::round doesn't work properly on arm-unknown-linux-gnueabi A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status I-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#122294 opened Mar 10, 2024 by vklachkov
7
rust-1.75.0 fails to compile with ICE on aarch64 and various ppc arches with LTO enabled - error: could not compile memchr A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-LTO Area: Link-time optimization (LTO) C-bug Category: This is a bug. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ 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 O-PowerPC Target: PowerPC processors P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#121124 opened Feb 15, 2024 by bowlofeggs
12
Tracking Issue for Bevy special-casing of implied bounds and -Zno-implied-bounds-compat C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC P-high High priority T-types Relevant to the types team, which will review and decide on the PR/issue.
#119956 opened Jan 14, 2024 by jackh726
x86-64 assembler silently truncates 64-bit address A-inline-assembly Area: Inline assembly (`asm!(…)`) 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 I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118223 opened Nov 24, 2023 by MauriceKayser
3
Building 1.74.0 natively on NetBSD/powerpc results in "pattern Some(_) not covered" error message A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-netbsd Operating system: NetBSD O-PowerPC Target: PowerPC processors P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118099 opened Nov 20, 2023 by he32
15
Errors compiling libc using rust 1.73.0 on riscv64/ubuntu:focal docker image - works with 1.72.1 A-linkage Area: linking into static, shared libraries and binaries C-bug Category: This is a bug. O-riscv Target: RISC-V architecture P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. regression-untriaged Untriaged performance or correctness regression. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#117101 opened Oct 23, 2023 by emlowe
5
Inlining causes miscompilation of code that mixes target features A-codegen Area: Code generation 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-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#116573 opened Oct 9, 2023 by RalfJung
57
Using thread_local! with Drop from GlobalAlloc::alloc causes crashes A-allocators Area: Custom and system allocators C-bug Category: This is a bug. P-high High priority T-libs Relevant to the library team, which will review and decide on the PR/issue.
#116390 opened Oct 3, 2023 by nvzqz
7
The ABI of float types can be changed by -Ctarget-feature A-ABI Area: Concerning the application binary interface (ABI) A-floating-point Area: Floating point numbers and arithmetic A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#116344 opened Oct 2, 2023 by RalfJung
42
Multiple nested loops taking very long to compile with CPU extensions A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-compiletime Issue: Problems and improvements with respect to compile times. P-high High priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#115465 opened Sep 2, 2023 by Ben-Lichtman
2
extern "C" fn on sparc64 targets does not respect repr(transparent) A-ABI Area: Concerning the application binary interface (ABI) A-FFI Area: Foreign function interface (FFI) I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-SPARC Target: SPARC processors P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#115336 opened Aug 29, 2023 by RalfJung
11
ProTip! Add no:assignee to see everything that’s not assigned.