Necromaticon

Results 5 comments of Necromaticon

```no_std``` issues with implementing ```panic_handler```

> The error says you should set `panic=abort`. Have you tried that? > > I doubt that cortex_m_rt supports unwinding, so panic=abort is likely what you want. First off thank...

```no_std``` issues with implementing ```panic_handler```

>Does RUSTFLAGS="-Cpanic=abort" cargo miri run help? I tried that just now and found the following behavior: With ```panic_abort``` when I run ```RUSTFLAGS="-Cpanic=abort" cargo run``` there is the same same where...

```no_std``` issues with implementing ```panic_handler```

>If you use #[start] you shouldn't also use #![no_main]. Also #[start] requires fn(isize, *const *const u8) -> isize as function signature. That did the trick for ```panic_halt``` and ```panic_abort```! I'm...

```no_std``` issues with implementing ```panic_handler```

>I don't think we want to implement support for each and every "program entry point" convention in Miri... I don't think that'd be necessary either. Since there is already a...

```--tests``` flag should enable ```#[test]``` attributes and behavior

Due to the state explosion problem caused by executing multiple functions in series, the ```--tests``` flag would execute the ```#[test]``` functions in isolation from each other, possibly by calling separate...