-
Notifications
You must be signed in to change notification settings - Fork 360
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
ICE around validation of bool
and char
#1467
Comments
I used this example (playground link). It only includes the code from |
Actually, even this ICEs: fn main() {
let _b: bool = unsafe { std::mem::MaybeUninit::uninit().assume_init() };
} Something is very odd... |
char
bool
and char
Actually |
After fixing the ICE, things are worse: there is no error at all... I'll need to do a full rustc bootstrap to get more debugging information, right now nothing makes any sense.^^ This will take a while. |
rust-lang/rust#74059 should fix this. |
…oli-obk Miri value validation: fix handling of uninit memory Fixes rust-lang/miri#1456 Fixes rust-lang/miri#1467 r? @oli-obk
@niluxv found an ICE around validation of uninitialized
char
. Here's a self-contained example; this embeds linked-hash-map. It would be nice to minimize this further.The actual ICE occurs here and it is unclear why, because uninitialized
char
usually work fine.The text was updated successfully, but these errors were encountered: