-
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
ICE with &[str] #24707
Comments
Yup! even syntax errors shouldn't crash the compiler. thanks for reporting. |
I cannot reproduce this from the given code in nightly: http://is.gd/XgQ75P (nor beta) @tzeskimo I think you need to provide more context from the code you wrote |
Note that any attempt to reproduce should ensure that debuginfo is being generated. |
@jdm Right - I'm probably missing something |
Reproducible running echo '#![crate_type="lib"]; fn a(_: &[str]){}' | rustc - -g This should fail at typecheck, I think, because |
cc #25470 |
cc #25388 |
Fixes rust-lang#21111. Fixes rust-lang#24707. Fixes rust-lang#24957. Fixes rust-lang#25388. Fixes rust-lang#25637. Fixes rust-lang#26301.
Fixed by #27641. |
Hi Folks,
Just ran into a compiler panic. I'm still learning rust, so it's probably related to a stupid syntax error on my part, but rustc suggested I file a bug report, so here I am...
Here's the error:
thread 'rustc' panicked at 'assertion failed: slice_layout_is_correct(cx, &member_llvm_types[..], element_type)', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/librustc_trans/trans/debuginfo.rs:2810
Here's the code I was writing:
Here's the backtrace:
Other Details:
The text was updated successfully, but these errors were encountered: