Skip to content
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

Update wasi-libc to latest HEAD #290

Merged
merged 2 commits into from
Jan 28, 2023

Conversation

abrown
Copy link
Collaborator

@abrown abrown commented Jan 26, 2023

This pulls in a variety of changes, many of them related to enabling threads in wasi-libc. There may be more changes necessary before releasing a prelease version of wasi-sdk that supports the new wasm32-wasi-threads target, but this should get the majority of them.

This pulls in a variety of changes, many of them related to enabling
threads in wasi-libc. There may be more changes necessary before
releasing a prelease version of wasi-sdk that supports the new
`wasm32-wasi-threads` target, but this should get the majority of them.
@abrown
Copy link
Collaborator Author

abrown commented Jan 26, 2023

@yamt, @loganek, @sbc100, others: any other wasi-libc PRs that you would like to see merged before a wasi-sdk prerelease is created. Here is the list open PRs: https://github.com/WebAssembly/wasi-libc/pulls. My suggestions (at least to discuss--open to rejecting as well): WebAssembly/wasi-libc#324, WebAssembly/wasi-libc#383.

@loganek
Copy link

loganek commented Jan 26, 2023

@abrown I still think we should merge WebAssembly/wasi-libc#324 (already resolved conflicts) but if anybody have a strong opinion about that, we can continue the discussion and postpone it.

@abrown
Copy link
Collaborator Author

abrown commented Jan 26, 2023

Merged WebAssembly/wasi-libc#324; any other opinions on WebAssembly/wasi-libc#383? It's similar in that it is an "enable weird features to support compatibility" change; wasi-libc does not have much to say about priority inheritance but that PR makes it appear as if it works.

@yamt
Copy link
Contributor

yamt commented Jan 27, 2023

any other opinions on WebAssembly/wasi-libc#383? It's similar in that it is an "enable weird features to support compatibility" change; wasi-libc does not have much to say about priority inheritance but that PR makes it appear as if it works.

as i commented in the PR, i feel it isn't ready even as an "just ignore the request saying ok" implementation. let's skip it for the prerelease.

@abrown
Copy link
Collaborator Author

abrown commented Jan 27, 2023

Ok, I closed WebAssembly/wasi-libc#383 and updated this PR with the now-merged WebAssembly/wasi-libc#324. After this PR merges, we should be ready for a wasi-sdk + threads prerelease.

@sunfishcode sunfishcode merged commit 7ef7e94 into WebAssembly:main Jan 28, 2023
@abrown abrown deleted the update-wasi-libc branch January 28, 2023 01:26
@yamt
Copy link
Contributor

yamt commented Feb 1, 2023

This pulls in a variety of changes, many of them related to enabling threads in wasi-libc. There may be more changes necessary before releasing a prelease version of wasi-sdk that supports the new wasm32-wasi-threads target, but this should get the majority of them.

do we plan to have a "official" prerelease in https://github.com/WebAssembly/wasi-sdk/releases ?
or at least a tag?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants