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.

Sign up for GitHub

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

Jump to bottom

Rename thread_spawn import #1907

Merged
merged 4 commits into from
Jan 26, 2023
Merged

Rename thread_spawn import #1907

merged 4 commits into from
Jan 26, 2023

Commits on Jan 25, 2023

  1. Rename thread_spawn import 

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

cf. WebAssembly/wasi-libc#387
    @yamt
    yamt committed Jan 25, 2023
    Configuration menu
    Copy the full SHA
    0a3e732 View commit details
    Browse the repository at this point in the history

  2. use the latest wasi-libc as samples/wasi-threads relies on it

    @yamt
    yamt committed Jan 25, 2023
    Configuration menu
    Copy the full SHA
    193f11d View commit details
    Browse the repository at this point in the history

  3. samples/wasi-threads: Update the target to match the latest wasi-libc

    @yamt
    yamt committed Jan 25, 2023
    Configuration menu
    Copy the full SHA
    efa6d2a View commit details
    Browse the repository at this point in the history

  4. samples/wasi-threads: Fix wasm app target 

    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.)
    @yamt
    yamt committed Jan 25, 2023
    Configuration menu
    Copy the full SHA
    b9947b2 View commit details
    Browse the repository at this point in the history