Skip to content

Issues: rust-lang/rust

Beta
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.

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

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
Assigned to nobody Loading
Sort

Issues list

Please stop using GITHUB_ACTION to change the behaviour of the build system C-discussion Category: Discussion or questions that doesn't represent real issues. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
#141813 opened May 31, 2025 by lu-zero
Tracking Issue for cfg_relocation_model C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC
#114929 opened Aug 17, 2023 by lu-zero
1 of 3 tasks
asm_sub_register warnings should provide an example/quick-fix A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#101163 opened Aug 29, 2022 by lu-zero
Infinite recursion when solving bounds A-trait-system Area: Trait system C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#99010 opened Jul 7, 2022 by lu-zero
--print=native-static-libs should behave as the other --print commands and not create output A-driver Area: rustc_driver that ties everything together into the `rustc` compiler A-frontend Area: Compiler frontend (errors, parsing and HIR) C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#61089 opened May 23, 2019 by lu-zero
Support uftrace (and other fentry consumers) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-feature-request Category: A feature request, i.e: not implemented / a PR. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#55092 opened Oct 15, 2018 by lu-zero
panic on failed dead code analysis A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#54553 opened Sep 25, 2018 by lu-zero
Altivec/VSX support A-intrinsics Area: Intrinsics A-SIMD Area: SIMD (Single Instruction Multiple Data) C-feature-request Category: A feature request, i.e: not implemented / a PR. O-PowerPC Target: PowerPC processors T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#42743 opened Jun 18, 2017 by lu-zero
ProTip! Type g i on any issue or pull request to go back to the issue listing page.