-
Notifications
You must be signed in to change notification settings - Fork 3.4k
[WIP] Merge musl-1.2.1 into #13006 #13007
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
base: main
Are you sure you want to change the base?
Conversation
Since I'm close would it help if I landed my musl upgrade and you could add your pthread fixes on top ? One thing I'm worried about is combining fixed with the musl upgrade. Ideally the upgrade could be as isolated as possible from other changes. |
That would certainly help. Let me know if you need help to resolve the CI failures.
I agree, this PR needs to be split up. I plan to make separate PRs for these changes:
|
That sounds great! Really appreciate the work you are doing here. Are there any of those patches we can split out and land now before the musl update? |
As far as I know, only bullet 1 and 4 needs to be done after the musl update, the rest can be done independently. (I actually tried to do bullet 1 with the current musl, but I didn't succeed, unfortunately) |
870e53a
to
8ad514f
Compare
51eafc3
to
1c60b3f
Compare
8d8cb24
to
be6e8fd
Compare
d24d4e3
to
7b7807e
Compare
9724bfb
to
8f7fa62
Compare
8a9d113
to
c08a603
Compare
All green now. Here's a list of changes that can land independently, in no order:
These changes require the musl update to land first (PR #13006):
Changes already landed or no longer needed: Details
I'll open PRs for the non-functional changes first, but let me know if some changes need to be prioritized. As always, any help would be greatly appreciated (I don't mind if these changes are landed by someone else). |
Wow! Thats a great amount of work. I will try to get #13006 landed soon so you can start landing some of these. Splitting out and landing the non-function stuff sounds like a great first step. |
b81af8a
to
e1bf2e6
Compare
b1fb2bb
to
5194c8a
Compare
569d1e7
to
415553b
Compare
415553b
to
b649159
Compare
b649159
to
06c03e4
Compare
06c03e4
to
a478bb7
Compare
d1a10c1
to
9b4ac22
Compare
9b4ac22
to
f26f6d5
Compare
f26f6d5
to
479d0ce
Compare
|
bc491af
to
d266e38
Compare
Mostly inspired by musl.
posixtest.test_pthread_cond_broadcast_1_2 seems to trigger this.
`exitRuntime()` is never called when `ENVIRONMENT_IS_PTHREAD` is true.
__has_feature(leak_sanitizer) cannot be used to detect the existence of LSan.
d266e38
to
37e9810
Compare
Just a test PR to see how this behaves in CI and to compare my changes with #13006. See #7279 for context.
Lines with
TODO(kleisauke):
needs some further investigation.