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
11 Open 25 Closed
11 Open 25 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

ICE: index out of bounds: the len is 0 but the index is 18446744073709551615 A-strict-provenance Area: Strict provenance for raw pointers C-bug Category: This is a bug. F-contracts `#![feature(contracts)]` 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.
#137588 opened Feb 25, 2025 by matthiaskrgr
@xizheyin
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
with_exposed_provenance(0).with_addr(addr) is compiled as gep null A-strict-provenance Area: Strict provenance for raw pointers C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#131741 opened Oct 15, 2024 by saethlin
5
Tracking Issue for strict_provenance_lints A-strict-provenance Area: Strict provenance for raw pointers C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue.
#130351 opened Sep 14, 2024 by RalfJung
10
Miscompilation with pointer address rountrip through address 0 A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-strict-provenance Area: Strict provenance for raw pointers C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#107326 opened Jan 26, 2023 by lukas-code
10
[strict provenance] Provide a way to "create allocations at a fixed address" A-strict-provenance Area: Strict provenance for raw pointers T-lang Relevant to the language 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. WG-embedded Working group: Embedded systems
#98593 opened Jun 27, 2022 by RalfJung
98
[strict provenance] Make The strict_provenance APIs Actual Compiler Magic? A-strict-provenance Area: Strict provenance for raw pointers T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#95498 opened Mar 30, 2022 by Gankra
6
[strict provenance] Fix System APIs That Are Liars A-strict-provenance Area: Strict provenance for raw pointers O-unix Operating system: Unix-like T-libs Relevant to the library team, which will review and decide on the PR/issue.
#95496 opened Mar 30, 2022 by Gankra
20
[strict provenance] make panic_unwind conform A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-strict-provenance Area: Strict provenance for raw pointers O-windows Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#95494 opened Mar 30, 2022 by Gankra
4
[strict provenance] Rationalize "Oxford Casts" A-strict-provenance Area: Strict provenance for raw pointers O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-wasm Target: WASM (WebAssembly), http://webassembly.org/ T-lang Relevant to the language team, which will review and decide on the PR/issue.
#95489 opened Mar 30, 2022 by Gankra
4
docs: clarify pointer provenance of Rc::as_ptr() A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-raw-pointers Area: raw pointers, MaybeUninit, NonNull A-strict-provenance Area: Strict provenance for raw pointers C-enhancement Category: An issue proposing an enhancement or a PR with one. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#87862 opened Aug 8, 2021 by y21
1
5
ProTip! Type g i on any issue or pull request to go back to the issue listing page.