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

Rename thread_spawn import #1907

Merged
merged 4 commits into from
Jan 26, 2023

Conversation

yamt
Copy link
Collaborator

@yamt yamt commented Jan 23, 2023

Following the wit-defined ABI:
WebAssembly/wasi-threads#26

cf. WebAssembly/wasi-libc#387

@yamt yamt marked this pull request as draft January 25, 2023 16:35
@yamt yamt force-pushed the rename-thread-spawn branch 3 times, most recently from 905a004 to aeb17ec Compare January 25, 2023 19:16
@yamt yamt marked this pull request as ready for review January 25, 2023 19:16
As far as I know, cmake can't handle two different compilers and
targets within a project as this sample is trying to do.
This commit is a band-aid fix.

While CMAKE_C_COMPILER_TARGET here happens to work when both of
host compiler and wasm compiler are clang, it doesn't seem working
if the host compiler is gcc. (as it is on the linux jobs on the CI.)
Copy link
Contributor

@wenyongh wenyongh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@loganek loganek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like duplication of #1912 so I'll close that PR and we can progress with this.

@wenyongh wenyongh merged commit 42f8fed into bytecodealliance:dev/wasi_threads Jan 26, 2023
victoryang00 pushed a commit to victoryang00/wamr-aot-gc-checkpoint-restore that referenced this pull request May 27, 2024
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.

3 participants