Large update to WASM Prism backend with Chicory#3902
Draft
Large update to WASM Prism backend with Chicory#3902
Conversation
org.jruby:chicory-prism
Nodes need access to RubySymbol and support APIs at least.
* It is a resource used as source code (in wasm) that is compiled for the project artifact. * Added to Rake CLOBBER
Allow the buffer functions to manage the internal pointer and use consistent argument order for calloc.
Primarily for testing purposes.
This is not all of the boot files but is sufficient to demonstrate a memory fault in the AOT WASM parser.
Fix the memory leak
Cleanup and improvements
Tweaks to WASM-based build for JVM
This is only intended to ever be used with JRuby 10+, which already requires Java 21.
* org.jruby.parser is base package for JRuby parsers * org.jruby.parser.prism is for parsers based on Prism * org.jruby.parser.prism.wasm is for the WASM Prism wrapper
headius
force-pushed
the
topic/javawasm_changes
branch
from
6d3a2f3 to
2235128
Compare
kddnewton
reviewed
Feb 3, 2026
Collaborator
kddnewton
left a comment
kddnewton
left a comment
There was a problem hiding this comment.
I'm generally fine with all of these changes. Would ruby-lang.org work?
Author
|
@kddnewton Something based on that domain would be fine, but no hyphens in Java package names. Too bad I would propose the following:
We'd need to register the group ID with the Maven Central folks (https://central.sonatype.org/register/namespace/#for-dns) and make sure anyone who wants to be able to publish Maven artifacts has access. For the moment I've got the WASM bits all under the following:
|
This moves all of the non-JRuby Java code from the org.prism package to the org.ruby_lang.prism package (corresponding to the ruby-lang.org domain and prism project).
Author
|
@kddnewton @enebo I believe this could be merged now and additional work done as smaller one-off PRs. This PR includes:
I have not:
This PR is now complete and sufficient to get an artifact for the WASM wrapper released to Maven Central for JRuby's use. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR includes a large set of changes to update the WASM backend using latest versions of Chicory and help from @andreaTP to clean it up and get it ready for a public release.
The changes here should not affect the existing native-library Java wrapper, but we will need to agree upon a package name and Maven groupID that represent a domain we have some control over (org.prism does not qualify since prism.org is completely unrelated to this project).
I would like to get Maven artifacts published for the native and WASM wrappers before JRuby 10.1 is released in the next few weeks.