Skip to content
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

Compiler crash: Expected label id but found style #14782

Closed
edef1c opened this issue Jun 9, 2014 · 3 comments
Closed

Compiler crash: Expected label id but found style #14782

edef1c opened this issue Jun 9, 2014 · 3 comments

Comments

@edef1c
Copy link
Contributor

edef1c commented Jun 9, 2014

rustc 0.11.0-pre (443a1cd 2014-06-08 14:56:52 -0700)
host: x86_64-unknown-linux-gnu
 ~/code/sulphur ⮀ ⭠ master± ⮀ make RUST_BACKTRACE=1
rustc -L vendor -g -O --crate-type staticlib --target x86_64-intel-linux -o kernel.a -Z lto src/kernel.rs
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug.
note: we would appreciate a bug report: http://doc.rust-lang.org/complement-bugreport.html
note: run with `RUST_BACKTRACE=1` for a backtrace
task 'rustc' failed at 'called `Result::unwrap()` on an `Err` value: Expected(Expected label id but found style)', /build/rust-git/src/rust/src/libcore/result.rs:545

stack backtrace:
   1:     0x7ff302a4d570 - rt::backtrace::imp::write::hf7f0193b62c10642jft::v0.11.0.pre
   2:     0x7ff302a54ca0 - <unknown>
   3:     0x7ff304dfef60 - unwind::begin_unwind_inner::hb191b1c2cc278613x2c::v0.11.0.pre
   4:     0x7ff304dfe9f0 - unwind::begin_unwind_fmt::hd9fbea452e71602eZZc::v0.11.0.pre
   5:     0x7ff304dfe9b0 - rust_begin_unwind
   6:     0x7ff304e46770 - failure::begin_unwind::h4ff9994309231abcSZv::v0.11.0.pre
   7:     0x7ff305732520 - middle::astencode::decode_inlined_item::h9446e2466a542596AUW::v0.11.0.pre
   8:     0x7ff305c758f0 - <unknown>
   9:     0x7ff305fbdd40 - metadata::decoder::maybe_get_item_ast::hd031e1bb33f639a1mMi::v0.11.0.pre
  10:     0x7ff305c74f40 - middle::const_eval::lookup_variant_by_id::h4bbc7dec36d34755rdW::v0.11.0.pre
  11:     0x7ff305879600 - middle::const_eval::lookup_const::h3a3853db3e30b204ycW::v0.11.0.pre
  12:     0x7ff305c77560 - <unknown>
  13:     0x7ff305c79ee0 - <unknown>
  14:     0x7ff305c79ee0 - <unknown>
  15:     0x7ff305c79ee0 - <unknown>
  16:     0x7ff305c7b360 - <unknown>
  17:     0x7ff305c7ae00 - <unknown>
  18:     0x7ff305c7ad00 - <unknown>
  19:     0x7ff305c7ac40 - <unknown>
  20:     0x7ff305c79ee0 - <unknown>
  21:     0x7ff305c79ee0 - <unknown>
  22:     0x7ff305c7ab60 - <unknown>
  23:     0x7ff305c79ee0 - <unknown>
  24:     0x7ff305c7ad00 - <unknown>
  25:     0x7ff305c7ac40 - <unknown>
  26:     0x7ff305c79ee0 - <unknown>
  27:     0x7ff305c7ad00 - <unknown>
  28:     0x7ff305c7ac40 - <unknown>
  29:     0x7ff305c7b9f0 - <unknown>
  30:     0x7ff305c7c080 - <unknown>
  31:     0x7ff305c7b360 - <unknown>
  32:     0x7ff305c7b360 - <unknown>
  33:     0x7ff305c79580 - middle::const_eval::process_crate::h72f6e727ec2afa69GnW::v0.11.0.pre
  34:     0x7ff305ffdd60 - driver::driver::phase_3_run_analysis_passes::h8c47e84f701a29a6DGn::v0.11.0.pre
  35:     0x7ff305ff7180 - driver::driver::compile_input::ha184fa62dc9d3b37dwn::v0.11.0.pre
  36:     0x7ff3060bf4a0 - <unknown>
  37:     0x7ff3060bf3c0 - <unknown>
  38:     0x7ff3060d9b80 - <unknown>
  39:     0x7ff3060d4e20 - <unknown>
  40:     0x7ff305146800 - <unknown>
  41:     0x7ff304dfc510 - <unknown>
  42:     0x7ff304e60ef0 - rust_try
  43:     0x7ff304dfe550 - unwind::try::h5e1236a7876941deTQc::v0.11.0.pre
  44:     0x7ff304dfc390 - task::Task::run::h10ae6b6004d94ab7qxc::v0.11.0.pre
  45:     0x7ff3051465a0 - <unknown>
  46:     0x7ff302a4c9c0 - <unknown>
  47:     0x7ff302783060 - start_thread
  48:     0x7ff304ad5489 - __clone
  49:                0x0 - <unknown>

Makefile:17: recipe for target 'kernel.a' failed
make: *** [kernel.a] Error 101
@alexcrichton
Copy link
Member

Could you provide a smaller example which triggers this error? If not, we could use creduce as well to slim down this use case.

@edef1c
Copy link
Contributor Author

edef1c commented Jun 10, 2014

It seems that recompiling the libraries I was using fixed this (I'm not sure why)

@alexcrichton
Copy link
Member

Ok, we have a few other issues open for using a stale library, such as #14748, so I'm going to close this in favor of those.

bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
Consider block impls in `lookup_impl_assoc_item_for_trait_ref`

fix rust-lang#14782
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants