Skip to content

Conversation

@qianxichen233
Copy link
Contributor

This PR is splited from PR #164

This PR focuses on spliting out the fix for __clone_internal_fallback function.

This could probably better be an issue rather a PR.

There is a weird bug on __clone_internal_fallback: when compiling some large applications, the generated wasm binary code at __clone_internal_fallback is incorrect and made the entire wasm binary unable to run. I currently havn't figured out if this is a bug from clang or it's due to something else. This is a very brutal temporary solution that directly removed the body of this function, this workaround at least made the compiled binary be able to run.

@rennergade
Copy link
Contributor

Lets leave this PR up for now and open up an issue.

At the very least if we do merge we need to add comments saying that we removed this and why.

@rennergade
Copy link
Contributor

I looked further into this and I think its fine to remove the function if its doing weird things when compiling, its only there to support systems that don't do clone3 and we do.

It's only called once in spawni if clone3 returns ENOSYS, we should probably add some sort of panic there if we got into a situation where it was somehow called. We definitely need to add comments here explaining as well.

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