-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix ESP-IDF constants and structs #3920
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
@JohnTitor Just to mention that this PR is a continuation of #3345 What we did is to
Obviously, we are running the comparison on the actual Espressif MCUs (or an emulation of those). And will likely continue doing so, in CI. |
@JohnTitor Sorry for the ping. Wondering if there is anything else we need to do so as this PR to be considered in a good shape for merging. |
?r @tgross35 Would you mind reviewing? The PR should be relatively uncontroversial in that it affects newlib/ESP IDF only and fixes obvious bugs (wrong definitions). |
@SergioGasquez Can you assign this to @tgross35 please? @JohnTitor @tgross35 if both of you are busy, would you suggest a reviewer that can look into this? |
?r @tgross35 |
?r @Amanieu |
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.
The non-espif newlib headers look correctly unchanged, if your tests indicate that things are fixed for espif then that seems reasonable to me. Please link headers in this PR if they are available.
Note that this repo just has a somewhat slow turn time for a handful of reasons, I keep an eye on all PRs even if they aren't assigned to me. (And the review request syntax is r?
, not ?r
).
(backport <rust-lang#3920>) (cherry picked from commit 133d9d0)
(backport <rust-lang#3920>) (cherry picked from commit 6f2b73a)
@MabezDev would it be possible to bump the libc dependency of the std crate on the next compiler build ? It would likely fix a lot of issues for a lot of people. Thanks as always ! |
Upstream already bumped the libc version, which was included in 1.84 nightly, so, worst case scenario we will have the changes in 2 releases, but maybe we could bump it for 1.83. |
This PR fixes some constants and structs which were wrong for ESP-IDF targets. I created an app that compares all the constants in
src/unix/newlib
andsrc/unix/newlib/espidf
modules with the ones in ESP-IDF source code (accessed viaesp_idf_svc::sys
). Here is the app https://github.com/SergioGasquez/libc-checks, usinglibc@0.2.158
yields the following errors:All those errors are fixed in this PR, if I point the app to use the branch of this PR, no errors appear.
cc and thanks to @ivmarkov!
closes #3774