rust --ls is now ICEing on every rust library I have tried it on. This is with rust from June 30 on Mac. For example doing an --ls on the library from https://github.com/jesse99/rust-socket results in:
gnos: rustc --ls bin/libsocket-9e5595de7eda745e-0.1.dylib
=Crate Attributes (9e5595de7eda745e)=
#[link(name = "socket",
vers = "0.1",
uuid = "AF82CEF5-A320-49C0-AE56-43129C5229D5",
url = "https://github.com/jdm/rust-socket")]
#[comment = "Rust socket library"]
#[license = "MIT"]
#[crate_type = "lib"]
socket_handle::sockfd (public field)
rust: task failed at 'describe_def: item not found (0, 3571)', /Users/jessejones/Source/Third_Party/rust/src/rustc/metadata/decoder.rs:551
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', /Users/jessejones/Source/Third_Party/rust/src/rustc/driver/rustc.rs:258
rust: domain main @0x7f934a800010 root task failed
rust: task failed at 'killed', /Users/jessejones/Source/Third_Party/rust/src/libcore/task.rs:461
Setting RUST_LOG didn't produce any additional output.
Just to be clear, your installed rustc was built from git HEAD as of June 30? That surprises me, because this looks like #2192 , which I fixed six days ago.
Ok, I'll try to reproduce.
Reproduced with 328fd30 -- I'll look into it.
This appears to be because the list-metadata code is trying to print out info about intrinsic::visit_ty, but the right information about it doesn't get serialized. Further research tomorrow.
Tag re-exports differently in metadata
so that the "list metadata" command doesn't print out anything
about intrinsics, but other code can see them.