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

Strange misbehaviour in life VM #73

Open
singpolyma-shopify opened this issue May 2, 2019 · 4 comments
Open

Strange misbehaviour in life VM #73

singpolyma-shopify opened this issue May 2, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@singpolyma-shopify
Copy link
Contributor

https://0x0.st/zcgm.wasm

The above wasm works in nodejs and using wagon's wasm-run command, but running with life I get a different return value.

Calling the exported function run with no arguments should return 4 and in nodejs and wasm-run it does but running under life I get 0.

I know it's a big blob but I have not yet been able to get a smaller version that triggers the bug.

@losfair
Copy link
Contributor

losfair commented May 3, 2019

Thanks for reporting the bug!

Could you try with Polymerase engine enabled? There's a known bug in the register allocator for interpreter mode.

@losfair losfair added the bug Something isn't working label May 3, 2019
@singpolyma-shopify
Copy link
Contributor Author

That's the AOT mode? When I enable that it takes a looong time and then says "unable to open compiled code"

@lowesyang
Copy link

Has this bug solved? Can life be used in production env?

@singpolyma-shopify
Copy link
Contributor Author

I haven't tested this specific case in awhile, but in general we have had much more luck with AOT (though you can't run it under many Docker setups because of the userfaultfd requirement)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants