-
Notifications
You must be signed in to change notification settings - Fork 1.3k
build.yml: Use a newer build toolchain #2306
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
Conversation
@tannewt let me know what direction you'd like to see this go in, now that we know there are failures due to binary size increases |
Let's close this for now. We can update along with CP 6. The Pirkey is hundreds of bytes over which will be hard to recover. |
@tannewt makes sense, couldn't have been predicted without the CI run... |
I'm looking at this again, there are some optimization flags we can set so that gcc9 behaves closer to gcc7 in terms of code size. I think this may let the most constrained m0 boards fit again. |
.. the new version is not offered in .deb form, so the installation process also changes
By tweaking the optimizer flags, we can get back a few hundred bytes and allow these builds to work with the gcc9 compiler.
By tweaking the optimizer flags further, this build also fits
pewpew10, pirkey_m0, and uchip all fit now. However, pirkey_m0 now has just 76 bytes flash available.
Sigh another board that doesn't fit |
.. inline-unit-growth was the same across all boards, and the highest max-inline-insns-auto parameter was shared across 2 of 5 boards, so it's worth a little work to follow the DRY principle
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Looks great! Thanks for sticking with this.
.. the new version is not offered in .deb form, so the installation process also changes
Problems: