Skip to content

Issues: rust-lang/rust

Draft release notes for 1.87
#140133 opened Apr 21, 2025 by BoxyUwU
Open 5
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
34 Open 38 Closed
34 Open 38 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

armv4t-none-eabi cannot use compiler_fence A-atomic Area: Atomics, barriers, and sync primitives A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140105 opened Apr 21, 2025 by EvansJahja
3
Atomic*::as_ptr unnecessarily restricts operations on the pointer to atomic operations A-atomic Area: Atomics, barriers, and sync primitives A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. T-opsem Relevant to the opsem team
#138246 opened Mar 8, 2025 by briansmith
1
atomic fences cause errors and atomic instructions are emitted without fences on nvptx64-nvidia-cuda A-atomic Area: Atomics, barriers, and sync primitives C-bug Category: This is a bug. 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.
#136480 opened Feb 3, 2025 by usamoi
4
atomic RMW intrinsics: avoid unnecessary ptr/int conversions A-atomic Area: Atomics, barriers, and sync primitives A-codegen Area: Code generation A-intrinsics Area: Intrinsics A-strict-provenance Area: Strict provenance for raw pointers C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such
#134617 opened Dec 21, 2024 by RalfJung
Using Release in the store operation for make_mut just prevent out-of-thin-air value? A-atomic Area: Atomics, barriers, and sync primitives C-discussion Category: Discussion or questions that doesn't represent real issues. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#133284 opened Nov 21, 2024 by xmh0511
Tracking issue for release notes of #122408: Use futex-based synchronization on Apple platforms A-atomic Area: Atomics, barriers, and sync primitives O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS) O-unix Operating system: Unix-like relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#132701 opened Nov 6, 2024 by rustbot
3 tasks
Can we avoid the heap allocation in macOS Mutex/Condvar? A-atomic Area: Atomics, barriers, and sync primitives C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such O-macos Operating system: macOS T-libs Relevant to the library team, which will review and decide on the PR/issue.
#131005 opened Sep 29, 2024 by RalfJung
1
Support 128-bit atomics on x86_64-fortanix-unknown-sgx A-atomic Area: Atomics, barriers, and sync primitives O-SGX Target: SGX 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.
#130552 opened Sep 19, 2024 by taiki-e Loading…
@wesleywiser
7
AtomicU128/AtomicI128 not shown in std docs on rust-lang.org A-atomic Area: Atomics, barriers, and sync primitives A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#130474 opened Sep 17, 2024 by programmerjake
--emit metadata produces less error messages with some targets A-atomic Area: Atomics, barriers, and sync primitives A-metadata Area: Crate metadata A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#129315 opened Aug 20, 2024 by japaric
Should Mutex and Condvar respect priorities? A-atomic Area: Atomics, barriers, and sync primitives C-discussion Category: Discussion or questions that doesn't represent real issues. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#128231 opened Jul 26, 2024 by joboet
10
std: use a queue-based Condvar on NetBSD and other platforms A-atomic Area: Atomics, barriers, and sync primitives O-netbsd Operating system: NetBSD O-SGX Target: SGX O-teeos Target: Arm's secure enclave that code isn't supposed to be able to jailbreak O-unix Operating system: Unix-like O-windows Operating system: Windows O-windows-7 OS: Windows 7 or Windows Server 2008 R2 or etc. O-xous OS: A microkernel OS for privacy in computing S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#127578 opened Jul 10, 2024 by joboet Loading…
@Mark-Simulacrum
19
Mutex/Once/OnceLock aren't guaranteed to have atomic acquire/release semantics A-atomic Area: Atomics, barriers, and sync primitives A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-discussion Category: Discussion or questions that doesn't represent real issues. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#126239 opened Jun 10, 2024 by briansmith
18
Use futex-based synchronization on Apple platforms A-atomic Area: Atomics, barriers, and sync primitives O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS) O-unix Operating system: Unix-like relnotes Marks issues that should be documented in the release notes of the next release. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#122408 opened Mar 12, 2024 by joboet Loading…
@m-ou-se
32
ABA-problem with pointer provenance in lockless queues A-atomic Area: Atomics, barriers, and sync primitives I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-medium Medium priority T-libs Relevant to the library team, which will review and decide on the PR/issue.
#121950 opened Mar 3, 2024 by joboet
11
Document memory ordering guarantees for std::thread::spawn() A-atomic Area: Atomics, barriers, and sync primitives A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-thread Area: `std::thread` C-feature-request Category: A feature request, i.e: not implemented / a PR. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#119519 opened Jan 2, 2024 by lukaslueg
1
Arc::strong_count memory ordering is a potential footgun A-atomic Area: Atomics, barriers, and sync primitives C-discussion Category: Discussion or questions that doesn't represent real issues. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#117485 opened Nov 1, 2023 by lukas-code
21
csky targets' atomic RMW is not lock-free A-atomic Area: Atomics, barriers, and sync primitives C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-csky Target: glaCSKY above covers over me~ P-low Low priority
#117306 opened Oct 28, 2023 by taiki-e
6
New atomic reference counting algorithm A-atomic Area: Atomics, barriers, and sync primitives perf-regression Performance regression. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#116173 opened Sep 26, 2023 by m-ou-se Loading…
@Amanieu
41
RwLock::read() should be reentrant so its behavior will be the same as borrow checker A-atomic Area: Atomics, barriers, and sync primitives T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#114770 opened Aug 13, 2023 by ultimaweapon
9
Atomic fetch_or fails to optimize right shift mask while left shift works A-atomic Area: Atomics, barriers, and sync primitives A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-slow Issue: Problems and improvements with respect to performance of generated code.
#114541 opened Aug 6, 2023 by SUPERCILEX
1
Tracking Issue for Atomic*::from_ptr and const_atomic_from_ptr A-atomic Area: Atomics, barriers, and sync primitives C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs Relevant to the library team, which will review and decide on the PR/issue.
#108652 opened Mar 2, 2023 by WaffleLapkin
3 tasks done
5
rustc emits calls to __sync_ when using load/store with +forced-atomics A-atomic Area: Atomics, barriers, and sync primitives 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. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#101300 opened Sep 2, 2022 by Lokathor
11
fetch_max broken for atomici8 and atomici16 on some targets. A-atomic Area: Atomics, barriers, and sync primitives A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#100650 opened Aug 16, 2022 by plugwash
18
How should we expose atomic load/store on targets that don't support full atomics A-atomic Area: Atomics, barriers, and sync primitives O-bare-metal Target: Rust without an operating system P-medium Medium priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#99668 opened Jul 24, 2022 by Amanieu
51
ProTip! Exclude everything labeled bug with -label:bug.