This repository was archived by the owner on Jan 24, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 83
Serious compile-time regression (1-2 min to 1 hour) #117
Comments
I'm seeing the same compile-time explosion even pinning cortex-m-rt to 0.5.4, so I'm not sure it's actually this crate's fault. Next up is bisecting nightlies. For reference rustc is spending all its time doing something like...
|
I can build stm32f3 fine with nightly-2018-08-30 (not bisected further) even with latest cortex-m-rt. So this is an issue but it's not cortex-m-rt's issue, I don't think. Looks like it's rust-lang/rust#54083 |
Thanks for finding! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, with the latest changes here I have seen a compile time regression from 1-2 min to now a little over 1 hour.
I am not sure what caused the regression, but it can be tested there (I have reproduced it on the latest nightly on both a Ubuntu 16.04 and Arch Linux distribution):
https://github.com/korken89/trustflight_firmware - enter the binary folder and run
cargo build --release
.The time is in @adamgreig's
stm32f3
crate in this case, which at the update to0.2.3
updated thecortex-m-rt
version (at0.2.2
this did not happen), leading me to place the issue here.Does anyone know what caused this to happen and a possible mitigation?
Thanks!
Rustc:
rustc 1.30.0-nightly (2d4e34ca8 2018-09-09)
Edit: Also, the compiler is not allocating any memory, which seems strange to me. Only allocating 107 MB and then not any change at all. Perhaps a compiler issue?
The text was updated successfully, but these errors were encountered: