-
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
Define c_char at top-level and remove per-target c_char definitions #4202
Conversation
I was concerned about whether this was backport friendly or not, but it turns out that it is not really a problem: #4203 |
☔ The latest upstream changes (presumably #4199) made this pull request unmergeable. Please resolve the merge conflicts. |
Some changes occurred in OpenBSD module cc @semarie |
(backport <rust-lang#4202>) (cherry picked from commit 8ab8323)
The exception was added after the PR with 0a02b94 ("Define c_char at top-level...") was posted. Remove this skip since the same commit makes it no longer relevant.
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.
I double checked everything here, looks like there are no further discrepancies. Pushed a commit that removes the last remaining c_char_def
skip, which was added in #4210.
Thanks for the cleanup!
(backport <rust-lang#4202>) (cherry picked from commit 0a02b94)
The exception was added after the PR with 0a02b94 ("Define c_char at top-level...") was posted. Remove this skip since the same commit makes it no longer relevant. (backport <rust-lang#4202>) (cherry picked from commit 2bb023e)
(backport <rust-lang#4202>) (cherry picked from commit 0a02b94)
The exception was added after the PR with 0a02b94 ("Define c_char at top-level...") was posted. Remove this skip since the same commit makes it no longer relevant. (backport <rust-lang#4202>) (cherry picked from commit 2bb023e)
Description
Replaces #4201
This is the approach I said I think is ideal in #4199 (comment).
It does not have the CI problem #4201 has.
Sources
Checklist
libc-test/semver
have been updated*LAST
or*MAX
areincluded (see #3131)
cd libc-test && cargo test --target mytarget
);especially relevant for platforms that may not be checked in CI