Test cargo-miri on Windows

[RalfJung]

No description provided.

[RalfJung]

Wrong size somewhere in the binops code... any good ideas how to debug this? Locally I'd use a rustc with tracing, but the nightlies don't have tracing.

thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `8`,
 right: `4`', src\librustc\mir\interpret\value.rs:288:17
stack backtrace:
   0: std::sys_common::alloc::realloc_fallback
   1: std::panicking::take_hook
   2: std::panicking::take_hook
   3: <rustc::ty::sty::Binder<rustc::ty::ProjectionPredicate<'tcx>> as rustc::ty::ToPredicate<'tcx>>::to_predicate
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: rustc::mir::interpret::value::Scalar<miri::stacked_borrows::Borrow, rustc::mir::interpret::AllocId>::to_bits<miri::stacked_borrows::Borrow>
             at <::std::macros::panic macros>:8
   8: rustc_mir::interpret::eval_context::EvalContext<miri::Evaluator>::binary_op<miri::Evaluator>
             at /rustc/adbfec229ce07ff4b2a7bf2d6dec2d13cb224980\src\librustc_mir\interpret\operator.rs:345
   9: rustc_mir::interpret::eval_context::EvalContext<miri::Evaluator>::binary_op_imm<miri::Evaluator>
             at /rustc/adbfec229ce07ff4b2a7bf2d6dec2d13cb224980\src\librustc_mir\interpret\operator.rs:294
  10: rustc_mir::interpret::eval_context::EvalContext<miri::Evaluator>::eval_rvalue_into_place<miri::Evaluator>
             at /rustc/adbfec229ce07ff4b2a7bf2d6dec2d13cb224980\src\librustc_mir\interpret\step.rs:169
  11: rustc_mir::interpret::eval_context::EvalContext<miri::Evaluator>::run<miri::Evaluator>
             at /rustc/adbfec229ce07ff4b2a7bf2d6dec2d13cb224980\src\librustc_mir\interpret\step.rs:50
  12: miri::eval_main::{{closure}}
             at .\src\lib.rs:167
  13: miri::eval_main::{{closure}}
             at .\src\lib.rs:167
  14: miri::after_analysis
             at .\src\bin\miri.rs:119

[oli-obk]

According to the trace we're executing a bin op https://github.com/rust-lang/rust/blob/master/src/librustc_mir/interpret/step.rs#L169

I'm guessing an earlier operation wrote a wrongly sized type to a local.

One thing is GetConsoleMode returning null, which is probably pointer sized, when the windows API says BOOL, which is probably int

[RalfJung]

One thing is GetConsoleMode returning null, which is probably pointer sized, when the windows API says BOOL, which is probably int

write_null uses the size of the destination, so that can't be it.

I hacked in some tracing, and it's GetStdHandle.