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
63 Open 68 Closed
63 Open 68 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Tracking issue for release notes of #140767: Stabilize sha512, sm3 and sm4 for x86 A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) 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-lang Relevant to the language team
#141822 opened May 31, 2025 by rustbot
Tracking issue for release notes of #140766: Stabilize keylocker A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) 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-lang Relevant to the language team
#141821 opened May 31, 2025 by rustbot
rustc_session: be more precise about -Z plt=yes on x86-64? A-codegen Area: Code generation A-linkage Area: linking into static, shared libraries and binaries C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such I-slow Issue: Problems and improvements with respect to performance of generated code. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141720 opened May 29, 2025 by iximeow
6
Tracking issue for release notes of #111137: Tracking Issue for AVX512 intrinsics F-stdarch_x86_avx512 `#![feature(stdarch_x86_avx512)]` O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) release-blog-post Marks issues tracking what text to put in the release blog post. 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-api Relevant to the library API team, which will review and decide on the PR/issue.
#141629 opened May 27, 2025 by rustbot
3
Stabilize sha512, sm3 and sm4 for x86 A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) S-waiting-on-documentation Status: Waiting on approved PRs to documentation before merging S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-lang Relevant to the language team to-announce Announce this issue on triage meeting
#140767 opened May 7, 2025 by sayantn Loading…
@scottmcm
19
Stabilize keylocker A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. I-lang-radar Items that are on lang's radar and will need eventual work or consideration. O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) S-waiting-on-documentation Status: Waiting on approved PRs to documentation before merging S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-lang Relevant to the language team to-announce Announce this issue on triage meeting
#140766 opened May 7, 2025 by sayantn Loading…
@traviscross
21
tests/codegen/lto-removes-invokes.rs spuriously fails on x86_64-pc-windows-gnu A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. O-windows-gnu Toolchain: GNU, Operating system: Windows O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139519 opened Apr 8, 2025 by jieyouxu
2
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-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.
#139370 opened Apr 4, 2025 by nsarlin-zama
25
Tracking Issue for APX target feature A-inline-assembly Area: Inline assembly (`asm!(…)`) 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 O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139284 opened Apr 2, 2025 by sayantn
3 tasks
3
Spurious SIGSEGV when building regex-automata (dep of stage 0 tool coverage-dump) on x86_64-apple-darwin in CI A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. CI-spurious-x86_64-apple-SIGSEGV-SIGILL CI spurious failure: SIGSEGV/SIGILL on x86_64-apple I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139245 opened Apr 2, 2025 by jieyouxu
pclmulqdq intrinsics don't inline well across target_feature changes anymore 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-prioritize Issue: Indicates that prioritization has been requested for this issue. I-slow Issue: Problems and improvements with respect to performance of generated code. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. S-has-bisection Status: A bisection has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139029 opened Mar 27, 2025 by iximeow
1
16
Tracking Issue for AVX10 target features 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 O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#138843 opened Mar 22, 2025 by sayantn
SIGSEGV/SIGILL while building rustc itself in x86_64 apple CI jobs A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. CI-spurious-x86_64-apple-SIGSEGV-SIGILL CI spurious failure: SIGSEGV/SIGILL on x86_64-apple I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134220 opened Dec 12, 2024 by jieyouxu
6
"rustc-LLVM ERROR" when using _mm_cvttps_epi32 on x86_64-unknown-none A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. C-bug Category: This is a bug. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133707 opened Dec 1, 2024 by eduardosm
2
How should we handle matrix ABIs? A-ABI Area: Concerning the application binary interface (ABI) C-discussion Category: Discussion or questions that doesn't represent real issues. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status O-AArch64 Armv8-A or later processors in AArch64 mode O-PowerPC Target: PowerPC processors O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133144 opened Nov 17, 2024 by workingjubilee
5
All interrupt ABIs should enforce either () or ! as return types A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-abi_x86_interrupt O-msp430 O-riscv Target: RISC-V architecture O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132841 opened Nov 10, 2024 by workingjubilee
extern "x86-interrupt" fn allows absurd signatures A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-abi_x86_interrupt O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132835 opened Nov 10, 2024 by workingjubilee
Directly calling "x86-interrupt" fn should be invalid A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-abi_x86_interrupt O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132834 opened Nov 10, 2024 by workingjubilee
False error: unknown x86 target feature: avx2 when passed to is_x86_feature_detected! as a literal instead of tt. A-target-feature Area: Enabling/disabling target features like AVX, Neon, etc. C-bug Category: This is a bug. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) 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.
#128586 opened Aug 3, 2024 by vcfxb
Tracking Issue for bf16 type in stdarch avx512 C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#127356 opened Jul 5, 2024 by sayantn
2 tasks
Tracking Issue for AVX512_FP16 intrinsics A-SIMD Area: SIMD (Single Instruction Multiple Data) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#127213 opened Jul 1, 2024 by sayantn
2 tasks
4
Tracking Issue for XOP target feature 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 O-x86_32 Target: x86 processors, 32 bit (like i686-*) (IA-32) O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
#127208 opened Jul 1, 2024 by sayantn
1 of 3 tasks
2
build-std + link-dead-code=y cannot build custom target without sse -Zbuild-std Unstable Cargo option: Compile the standard library yourself. 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) requires-nightly This issue requires a nightly compiler in some way.
#123494 opened Apr 5, 2024 by jzbor
5
Indexing with bool generates suboptimal assembly A-codegen Area: Code generation C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such I-slow Issue: Problems and improvements with respect to performance of generated code. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue
#122121 opened Mar 7, 2024 by alion02
4
SEE-AVX-stall when using target-cpu=znver2. Thus ~25 times slower. A-codegen Area: Code generation 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 I-slow Issue: Problems and improvements with respect to performance of generated code. O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#120108 opened Jan 18, 2024 by Barfussmann
5
ProTip! Add no:assignee to see everything that’s not assigned.