-
Notifications
You must be signed in to change notification settings - Fork 259
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
Implement initial optimizing compiler backend: project wazevo #1496
Labels
enhancement
New feature or request
Comments
So we call this new backend |
mathetake
changed the title
Implement initial optimizing compiler backend
Implement initial optimizing compiler backend: project wazevo
Jun 1, 2023
This was referenced Aug 8, 2023
This was referenced Aug 16, 2023
This was referenced Aug 19, 2023
This was referenced Oct 23, 2023
This was referenced Oct 23, 2023
This was referenced Oct 30, 2023
This was referenced Oct 31, 2023
This was referenced Nov 2, 2023
This was referenced Nov 9, 2023
This was referenced Nov 20, 2023
This was referenced Dec 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is the first tracking issue for our frequently requested feature: the optimizing compiler backend. For background, see #777 (comment).
The ultimate goal is to develop the optimizing compiler backend which has support for arm64 and amd64 and has an equivalent performance as the state-of-the-art compilers like wasmtime or wasmer. But that work is never-ending considering that every compiler evolves over time.
Thus, this issue exists for tracking the work around building the foundation for the never-ending iterative development of our new optimizing compiler.
Goal (to close this issue):
Non-Goal
Note
so for those easger to contribute, please fight your urge to do so until my first PoC is out (I am expecting it up within July).The text was updated successfully, but these errors were encountered: