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

Backends #1

Open
2 of 8 tasks
phase opened this issue Nov 19, 2016 · 0 comments
Open
2 of 8 tasks

Backends #1

phase opened this issue Nov 19, 2016 · 0 comments
Labels

Comments

@phase
Copy link
Owner

phase commented Nov 19, 2016

We need to organize what backends we want and how we're going to build them.

  • LLVM: As the most optimized backend, LLVM is great for speed, but can be bad for compile times.

  • JVM: ASM will probably be the library we use.

  • Parrot: Parrot's IR is very simple but doesn't have complex types.

  • NekoVM: Neko should be easy to compile to.

  • WASM/JS: Putting the language on the web will be cool, and WASM gives us the static typing and speed we want.

  • B3: Webkit's new backend seems promising, and using JavaCPP will make it easy to call.

  • Cretonne: A Rust backend might be hard to call.

  • MoarVM

@phase phase added the feature label Nov 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant