Skip to content

README: clarify hardware support and fallback mechanism + more exact origin of assembly code #3

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

Open
matu3ba opened this issue Apr 10, 2024 · 3 comments

Comments

@matu3ba
Copy link

matu3ba commented Apr 10, 2024

First of, this looks very nice.

Luajit does not support all targets,
so it would be nice to have the supported platforms as matrix, ideally in section Features.

Further more, it would be nice to have the exact commit hashes the assembly was created from.

@tidwall
Copy link
Owner

tidwall commented Apr 10, 2024

Platform Assembly Method Fallback
Linux ARM/ARM64/x86_64/rv64 ucontext
Mac ARM64/x86_64 ucontext
BSD ARM64/x86_64 ucontext
Windows x86_64 N/A
WebAssembly N/A Asyncify

The assembly code in Neco is from the embedded packages https://github.com/tidwall/sco and https://github.com/tidwall/llco. Those packages use assembly from the minicoro library (MIT-0), specifically edubart/minicoro@ff5321d. The minicoro assembly implementation is inspired by Lua Coco by Mike Pall.

@calvin2021y
Copy link

what about ios/android support ?

@tidwall
Copy link
Owner

tidwall commented Apr 11, 2024

@calvin2021y I haven’t tested on those platforms. It may work with minimal tweaking, since both have posix apis that are similar to Mac and Linux.

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

No branches or pull requests

3 participants