-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
STATUS_ACCESS_VIOLATION
when cross-compiling for nightly-2024-02-19-aarch64-pc-windows-msvc when compiling num-traits
#121367
Labels
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
C-bug
Category: This is a bug.
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
llvm-fixed-upstream
Issue expected to be fixed by the next major LLVM upgrade, or backported fixes
Comments
rustbot
added
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Feb 20, 2024
chyyran
changed the title
Feb 21, 2024
STATUS_ACCESS_VIOLATION
on nightly-2024-02-19-aarch64-pc-windows-msvc when compiling num-traits
STATUS_ACCESS_VIOLATION
when cross-compiling for nightly-2024-02-19-aarch64-pc-windows-msvc when compiling num-traits
nikic
added
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
and removed
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Feb 21, 2024
Reduced: ; RUN: llc -O0 < %s
target triple = "aarch64-pc-windows-msvc"
define float @test(float %x, i32 %n) {
%res = call float @llvm.powi.f32.i32(float %x, i32 %n)
ret float %res
}
declare float @llvm.powi.f32.i32(float, i32) Does not reproduce on LLVM trunk. |
nikic
added
the
llvm-fixed-upstream
Issue expected to be fixed by the next major LLVM upgrade, or backported fixes
label
Feb 21, 2024
Fixed by llvm/llvm-project@47c65cf and already backported upstream. |
This was referenced Feb 21, 2024
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 21, 2024
Update to LLVM 18.1.0 rc 3 Fixes rust-lang#120819. Fixes rust-lang#121180. Fixes rust-lang#121239. Fixes rust-lang#121367.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 22, 2024
Update to LLVM 18.1.0 rc 3 Fixes rust-lang#120819. Fixes rust-lang#121180. Fixes rust-lang#121239. Fixes rust-lang#121367.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 22, 2024
Update to LLVM 18.1.0 rc 3 Fixes rust-lang#120819. Fixes rust-lang#121180. Fixes rust-lang#121239. Fixes rust-lang#121367.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 22, 2024
Update to LLVM 18.1.0 rc 3 Fixes rust-lang#120819. Fixes rust-lang#121180. Fixes rust-lang#121239. Fixes rust-lang#121367.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 24, 2024
Update to LLVM 18.1.0 rc 3 Fixes rust-lang#120819. Fixes rust-lang#121180. Fixes rust-lang#121239. Fixes rust-lang#121367.
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 1, 2024
Update to LLVM 18.1.0 rc 3 Fixes rust-lang#120819. Fixes rust-lang#121180. Fixes rust-lang#121239. Fixes rust-lang#121367.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
C-bug
Category: This is a bug.
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
llvm-fixed-upstream
Issue expected to be fixed by the next major LLVM upgrade, or backported fixes
Minimal reproducible example
cargo build --target aarch64-pc-windows-msvc
I expected to see this happen:
cargo builds the example
Instead, this happened:
The last working compiler that I've tried was
nightly-2024-01-15-aarch64-pc-windows-msvc
. I haven't attempted to bisect since then so there could be some compilers working after 2024-01-15.The text was updated successfully, but these errors were encountered: