Creating a JVM language
jakubdziworski.github.io
jakubdziworski.github.io
Writing a Language in Truffle: http://cesquivias.github.io/tags/truffle.html
You can talk to the Graal and Truffle teams directly on https://gitter.im/graalvm/graal-core if you can't find where to start or have questions.
I lead the Ruby implementation https://github.com/jruby/jruby/tree/master/truffle which along with FastR is one of the most sophisticated open-source users of Truffle and Graal.
http://docklandsljc.uk/2016/04/truffle-graal-clojure-neo4j.h...
I guess it's also theoretically possible to have a bytecode backend for Graal, but that wouldn't make sense except maybe to make Truffle languages executable on non-Graal JVMs for compatibility; I don't know how useful it would be because I think Truffle has an interpreter fallback.
I hope Graal converts both JVM bytecode and Truffle ASTs directly into an internal SSA form, without first building an AST from JVM bytecode.
Actually, come to think of it, if I were a Graal author, I'd be tempted to have a JVM bytecode interpreter, two non-optimizing Wirth-style compilers that emitted native code directly from JVM bytecode and Truffle ASTs, two middle-ends that generated SSA from JVM bytecode and Truffle ASTs, and an optimizing SSA-based native code back-end.
> I don't know how useful it would be because I think Truffle has an interpreter fallback.
Every Truffle AST node contains Java code for evaluating that node, so a tree-walking interpreter is trivial.
This is an incredibly well-made project.
(Also, I love the Polish in-jokes. :)
You can't just say that and leave us hanging!
Dupa is often used as 'foo' variable by Polish programmers and used to be most popular password (like qwerty).
[1]http://jakubdziworski.github.io/enkel/2016/03/23/enkel_5_cla...