-
Notifications
You must be signed in to change notification settings - Fork 220
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
Updates for Xtensa enabled 1.83 compiler #2615
Conversation
2b680a0
to
a6c5233
Compare
@@ -772,7 +772,7 @@ fn lint_package(path: &Path, args: &[&str], fix: bool) -> Result<()> { | |||
// build in release to reuse example artifacts | |||
let cargo_args = builder.arg("--release"); | |||
let cargo_args = if fix { | |||
cargo_args.arg("--fix").arg("--lib") | |||
cargo_args.arg("--fix").arg("--lib").arg("--allow-dirty") |
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.
Thank you, keep forgetting to add this 😅
Any updates here? |
Nothing yet, the LLVM issue is being looked into still. Our last resort is still available, which is to bump the MSRV. |
Issue is fixed 🎉 , needs to make its way to github and I'll start the release builds |
8bf4031
to
41a877b
Compare
Well, it's fixed... but we're still in a situation where MSRV is failing because the bug that I found whilst trying to avoid bumping MSRV also affects the MSRV toolchain 🙃. I think we have a few options here:
Thoughts? |
Getting rid of naked functions sounds best to me. Not ideal to bump MSRV to 1.83 however. Not sure how much effort option 3 would be |
0f2ddfd
to
e145858
Compare
I went for the first option. When CI is green, I'll promote the compiler release to stable and remove the hardcoded versions from the workflows here. |
28497a0
to
f5c5d5c
Compare
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.
LGTM - I also briefly tested with some esp-wifi examples and they still work fine
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.
LGTM, thanks!
(@bugadani will review this too, please don't merge yet) |
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.
ASM changes look OK.
Crate MSRVs are still set to 1.79, is that intentional? MSRV bump is also missing from the changelogs - although the label is set, we used to call out these changes.
e.g. in esp-hal:
Line 5 in f5c5d5c
rust-version = "1.79.0" |
Thanks, I always forget about the |
253d3bc
to
84eac23
Compare
All of my xtensa projects are failing to build, do I have to use the github repo as the source for the esp-hal package? For how long? |
Please kindly downgrade your compiler with |
Thx, I didn't know I could install different versions of tool chains with espup. |
Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝
cargo xtask fmt-packages
command to ensure that all changed code is formatted correctly.CHANGELOG.md
in the proper section.Extra:
Pull Request Details 📖
Description
Please provide a clear and concise description of your changes, including the motivation behind these changes. The context is crucial for the reviewers.
Testing
Describe how you tested your changes.