-
Notifications
You must be signed in to change notification settings - Fork 13.3k
1.46.0-nightly panics on a particular proc macro invocation #73993
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
|
Also occured with |
I'm getting this when I try to repro:
On a side note, are there any cargo feature flags I can pass to cut down on how much stuff is being compiled? Compiling 900 crates to get a repo is quite a lot 🙂 |
Also occured with |
mmh try with commit hash |
updated script: git clone git@github.com:hicommonwealth/edgeware-node.git
cd edgeware-node
git checkout 893981a2f2fdff8b3e6b0dddf4cf7ad4f9a09dfe
rustup override set nightly-2020-06-28
rustup target add wasm32-unknown-unknown --toolchain nightly-2020-06-28-x86_64-unknown-linux-gnu
cargo build --release -p edgeware-runtime |
Yeah, sorry for that. One of the difficulties of working with a big framework like Substrate. I'll see if I can narrow it down more. |
That did it! Thank you 🙂 |
Some with the same issue (a different chain also using Substrate) found out that |
Seems #73513 is the cause, marking as |
Here's a smaller repro (at least in terms of how much code is built: 33 crates instead of a few hundred):
|
just confirmed that it does not occur with |
I have a minimal repro: pub struct Fixed64(i64);
pub fn div(f: Fixed64) {
f.0 / 0;
} |
Fix const prop ICE we used to erase the local just before we tried to read it for diagnostics fixes rust-lang#73993 r? @wesleywiser
@wesleywiser I seem to be getting a similar error again on a more current nightly (
|
@oli-obk This is still broken. I'm pretty confused because running the test you added in #74102 on the playground shows that it ICEs. Is the test not actually working for some reason? Edit: Does that test need |
Don't panic if the lhs of a div by zero is not statically known Fixes rust-lang#73993 for real this time r? @wesleywiser
Don't panic if the lhs of a div by zero is not statically known Fixes rust-lang#73993 for real this time r? @wesleywiser
Don't panic if the lhs of a div by zero is not statically known Fixes rust-lang#73993 for real this time r? @wesleywiser
Assigning |
Don't panic if the lhs of a div by zero is not statically known Fixes rust-lang#73993 for real this time r? @wesleywiser
Don't panic if the lhs of a div by zero is not statically known Fixes rust-lang#73993 for real this time r? @wesleywiser
Don't panic if the lhs of a div by zero is not statically known Fixes rust-lang#73993 for real this time r? @wesleywiser
I've updated to rust version 1.47.0-nightly (bbebe73 2020-07-22), and tried compiling the crate which was triggering this ICE ( |
I can confirm |
Great, thank you! |
UPDATE: MCVE can be found here.
Nightly compilation error due to rustc bug
I tried this code:
https://github.com/paritytech/substrate/blob/master/frame/support/procedural/src/construct_runtime/mod.rs#L31-L425
I expected to see this happen: explanation
Successful compilation.
Instead, this happened:
rustc
tells to report a bug, see backtrace.Meta
rustup run nightly rustc --version --verbose
:Reproduce with
(1st update)
Backtrace
The text was updated successfully, but these errors were encountered: