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
36 Open 45 Closed
36 Open 45 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

compiler_fence example is misleading A-atomic Area: Atomics, barriers, and sync primitives A-concurrency Area: Concurrency A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#133014 opened Nov 13, 2024 by lukas-code
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
Document what a "dangling pointer" is A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. E-help-wanted Call for participation: Help is requested to fix this issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#132286 opened Oct 28, 2024 by Urgau
3 tasks
13
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
Compilation error when matching reference to empty enum A-exhaustiveness-checking Relating to exhaustiveness / usefulness checking of patterns A-patterns Relating to patterns and pattern matching C-bug Category: This is a bug. F-exhaustive_patterns `#![feature(exhaustive_patterns)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team T-types Relevant to the types team, which will review and decide on the PR/issue.
#131452 opened Oct 9, 2024 by dhedey
@Nadrieril
26
Further restricting what coercions are allowed on places of type ! A-coercions Area: implicit and explicit `expr as Type` coercions C-discussion Category: Discussion or questions that doesn't represent real issues. F-never_type `#![feature(never_type)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#131297 opened Oct 5, 2024 by compiler-errors
6
Unexpected unsizing coercion introduced by unsafe block A-MIR Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html T-opsem Relevant to the opsem team T-types Relevant to the types team, which will review and decide on the PR/issue.
#128880 opened Aug 9, 2024 by RalfJung
3
Can CFI be made compatible with type erasure schemes? A-sanitizers Area: Sanitizers for correctness and code quality C-discussion Category: Discussion or questions that doesn't represent real issues. PG-exploit-mitigations Project group: Exploit mitigations T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#128728 opened Aug 6, 2024 by RalfJung
19
Miscompilation of a program projecting field of an extern type A-mir-opt Area: MIR optimizations C-bug Category: This is a bug. F-extern_types `#![feature(extern_types)]` 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 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. T-opsem Relevant to the opsem team
#127336 opened Jul 4, 2024 by tmiasko
What should SIMD bitmasks look like? A-SIMD Area: SIMD (Single Instruction Multiple Data) C-discussion Category: Discussion or questions that doesn't represent real issues. PG-portable-simd Project group: Portable SIMD (https://github.com/rust-lang/project-portable-simd) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#126217 opened Jun 10, 2024 by RalfJung
6
Allow moving out of &'static mut T C-discussion Category: Discussion or questions that doesn't represent real issues. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#125868 opened Jun 1, 2024 by Ddystopia
17
Tracking Issue for RFC 3467: UnsafePinned B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-unsafe_pinned `#![feature(unsafe_pinned)]` T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#125735 opened May 29, 2024 by traviscross
1 of 6 tasks
2
How should const generics with references work around pointer identity and padding? A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) F-unsized_const_params `#![feature(unsized_const_params)]` T-opsem Relevant to the opsem team
#120961 opened Feb 12, 2024 by RalfJung
1
15
What is the behavior of a place-to-value/reference conversion of a variant place? T-opsem Relevant to the opsem team
#120369 opened Jan 26, 2024 by RalfJung
3
Poor codegen for derived == on simple 2-field struct A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. I-slow Issue: Problems and improvements with respect to performance of generated code. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#117800 opened Nov 11, 2023 by scottmcm
4
Guarantee that it is sound to observe the bytes of None::<P> where P is a pointer type subject to NPO A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools T-lang Relevant to the language team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#117591 opened Nov 4, 2023 by joshlf
Move alignment checks to codegen 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-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#117473 opened Nov 1, 2023 by saethlin • Draft
@wesleywiser
64
The extern "C" ABI of SIMD vector types depends on target features (tracking issue for abi_unsupported_vector_types future-incompatibility lint) A-ABI Area: Concerning the application binary interface (ABI) A-SIMD Area: SIMD (Single Instruction Multiple Data) A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-simd_ffi `#![feature(simd_ffi)]` I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness 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-opsem Relevant to the opsem team
#116558 opened Oct 9, 2023 by RalfJung
37
invalid_reference_casting lint catches some patterns that aren't UB A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. C-bug Category: This is a bug. L-invalid_reference_casting Lint: invalid_reference_casting T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#116410 opened Oct 4, 2023 by LegionMammal978
1
18
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
40
FCP process: Require 2/3 majority for FCP 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. T-opsem Relevant to the opsem team T-release Relevant to the release subteam, which will review and decide on the PR/issue.
#114986 opened Aug 19, 2023 by RalfJung
39
Can Weak be null? A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. T-opsem Relevant to the opsem team
#114517 opened Aug 5, 2023 by est31
1
5
The ref to *const implicit conversion has become a footgun with e.g. Rc::from_raw C-discussion Category: Discussion or questions that doesn't represent real issues. T-opsem Relevant to the opsem team
#112337 opened Jun 6, 2023 by glandium
17
Clarify drop_in_place safety S-waiting-on-team Status: Awaiting decision from the relevant subteam (see the T-<team> label). T-opsem Relevant to the opsem team
#108684 opened Mar 3, 2023 by Manishearth Loading…
@JakobDegen
30
repr(Rust) unions (including MaybeUninit) do not preserve padding bytes T-opsem Relevant to the opsem team
#99604 opened Jul 22, 2022 by 5225225
10
ProTip! no:milestone will show everything without a milestone.