The OpenLDK is very interesting - it looks like it “compiles” to the vintage procedural dialect within CL (eg TAGBODY etc.) I wonder if someone’s ever bypassed the “procedural Lisp” level and just used a CL implementation’s internal assembler interactively, though. (IIRC both SBCL and CCL expose theirs.)
TAGBODY/GO are broadly used in advanced Lisp macros. If you expand a non-trivial extended LOOP invocation you'd likely see some.
If you compile to an implemenation's assembler (even where that possible) you don't really compile into Lisp anymore. And really the Lisp compiler is going to do a better job at generating machine code.
I haven't tried it, but the description sounds delightfully perverse. And an LLM (Claude) cannot be embarrassed by perverting Lisp/Scheme with Java.
Why should it?
"We were after the C++ programmers. We managed to drag a lot of them about halfway to Lisp." -- Guy Steele
And? Do you want a medal for plagiarizing other people's work?