1.68.0 emits STATUS_ILLEGAL_INSTRUCTION on build

[rozensoftware]

Couldn't build with cargo build.
I tried this code:

fn main() {
    println!("Hello, world!");
}

I expected to see this happen:

the program should compile fine.

Instead, this happened:

error: could not compile nanny

Caused by:
process didn't exit successfully: rustc --crate-name nanny --edition=2021 src\main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=203 --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=5a2abc74c1c30893 --out-dir D:\Projects\nanny\target\debug\deps -C incremental=D:\Projekty\nanny\target\debug\incremental -L dependency=D:\Projects\nanny\target\debug\deps (exit code: 0xc000001d, STATUS_ILLEGAL_INSTRUCTION)

rustc --version --verbose:

rustc 1.68.0 (2c8cc3432 2023-03-06)
binary: rustc
commit-hash: 2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74
commit-date: 2023-03-06
host: x86_64-pc-windows-msvc
release: 1.68.0
LLVM version: 15.0.6

Notes:

cargo check emits the same error.
cargo build --release works correctly.

Having Visual Studio 2022 v17.5.1 installed on my system.

[workingjubilee]

That's... weird.
What CPU/Windows OS are you running on?

[rozensoftware]

CPU: AMD Phenom(tm) II X4 840 Processor 3.20 GHz
OS: Windows 10 Pro 64bit, 22H2

[workingjubilee]

Huh.
Did a prior version of Rust work?

I do know the CPU you are using pushes the edges of Windows 10 support. I would have thought it was still "in the clear", but only barely. I'd ask you to attach a debugger to find where the illegal instruction is invoked but I am not really familiar with the Windows debugging tools.

[rozensoftware]

Yes, previous version of Rust did work fine. I have dual booting computer with Linux also. 1.68 compiles correctly mentioned above code on Linux (and other projects also).
I am very sorry, but currently I do not have a ready environment to perform the above test.
I am aware that processor is old. But still, it's a mystery why this happened..

[workingjubilee]

So Windows fails, but Linux does not?
I don't know how to explain that...

[workingjubilee]

Oh.This might be a consequence of a double-panic...

[rozensoftware]

I'm glad you have found something. Yes, this fails only on Windows on my system configuration.

[GregGorin]

I have the same problem. CPU AMD Phenom II X6 1090T

[Kronprinz42]

I have the same problem. I used the standalone installer. Core 2 Duo E6320 processor. However, when using "cargo build --release" everything compiles successfully.

[BloodSharp]

Hello, I'm having the same issue with AMD Phenom II X4 945 CPU and Windows 11 Pro, building using "cargo build --release" seems to work.

rustc 1.68.0 (2c8cc3432 2023-03-06)
binary: rustc
commit-hash: 2c8cc343237b8f7d5a3c3703e3a87f2eb2c54a74
commit-date: 2023-03-06
host: x86_64-pc-windows-msvc
release: 1.68.0
LLVM version: 15.0.6

PS: The stable-i686-pc-windows-msvc toolchain seems to work both on debug and release mode.

[lqd]

Could you try on nightly ? Especially the latest one, nightly-2023-03-14 for rustup, rustc 1.70.0-nightly (22f247c6f 2023-03-13) for rustc -vV.

I wonder if it's linked to the ThinLTO miscompilation #109067.

[ehuss]

Also, if nightly doesn't help, can you try to use a debugger to see where it is faulting? You should be able to launch a debugger on rustc (the path can be shown via rustup which rustc), and copy the command-line arguments in. This can be done in Visual Studio if you have that installed.