-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Bug in Rustc Version 1.77 #120349
Comments
Can you say more about why this appears to be a new issue? From what I can tell, this test fails on all versions of Rust. The test appears to be x86-specific. That is, on ARM, the alignment of a 128-bit value is 16, not 8 as it is on x86_64 architectures. |
Hey, sry i am not an expert in the byte spectrum. The error first appeared on my x86_64 Linux Machine. Later i tested the Code again on my Arm Notebook. A friend of did test the Code on x86_64 Intel too to close the circle. Yeah the bug seems to be plattform independent. |
sry, i have to sleep, i will test again to more once. again on x86_64 machine to see if the are different Values. But the Code failed on the same Line. |
I have no glue. It was an dependency my Code, just figured out which crate failed and started to test the Code of time-rs against different rust Versions. It seems it still works in 1.75 and 1.76. worked (Sry to say it was tested on x86_64). 1.77 failed compiling |
Ah, I see what you are saying now. This was an intentional change as part of #116672 to update the alignment of 128-bit types on x86. |
Additionally, the alignments of integer types are explicitly not guaranteed.
|
I will send the backtrace of my own code later. |
Thank you for the report, but this is an expected change as mentioned above. You need to update the test (or remove it, I'm not sure why it would be useful to have). |
It's occasionally useful to have layout tests to ensure that you don't accidentally change layout of something critical. Rustc even has many of these for some of its most commonly used types. But occasionally something like this happens which is out of your control and you just have to update the test and move on. |
Ok, unfortunately I couldn't reconstruct the error in my own Code |
Hey, i noticed an error in One of my deps, this error just started to get up on the Rust Nightly Version.
First Noticed on Version 1.77 2024-01-17
It was tested on Arm M2 MacBook and Arch Linux AMD x86_64.
The error stayed the same.
Repo: https://github.com/time-rs/time
File: https://github.com/time-rs/time/blob/main/time/src/parsing/parsed.rs
Line of the trait Parsed that fails in Line 116.
The Compiler fails to compile the Code of a function that mutates an byte Sequenz.
I tried this code:
I expected to see this happen: explanation
Instead, this happened: explanation
Meta
rustc --version --verbose
:Backtrace
The text was updated successfully, but these errors were encountered: