Christian Bartolomäus
Christian Bartolomäus
Hi Fabrice, I can't give you an authoritative answer regarding the future of the JVM backend, but can only describe my subjective view. Since a couple of years (I'd say...
I've opened a second, more general issue for the implementation of nqp::substr: https://github.com/perl6/nqp/issues/533. Nevertheless, I'll leave this issue open for now.
To make things a bit clearer, I'll post the output with the following debug statements added: ``` diff --git a/src/core.c/Encoding/Decoder/Builtin.pm6 b/src/core.c/Encoding/Decoder/Builtin.pm6 index d9a1e2ca6..699328d56 100644 --- a/src/core.c/Encoding/Decoder/Builtin.pm6 +++ b/src/core.c/Encoding/Decoder/Builtin.pm6 @@ -70,6...
Well, from the looks of it porting the following (related) fixes to the JVM backend could help: * https://github.com/MoarVM/MoarVM/commit/0f7277a670 * https://github.com/rakudo/rakudo/commit/6bb8823794 Also ```nqp::p6capturelexwhere``` is not available for the JVM backend...
I've tested this on my FreeBSD box and I think I've seen somewhat lower build times than usual. If no-one objects, I'll merge this PR in a few days.
@ugexe unfortunately merging the s/perl6/raku rename (https://github.com/Raku/nqp/pull/630) caused a conflict for this PR. If I'm not mistaken the change to ```src/vm/jvm/runtime/org/perl6/nqp/runtime/Ops.java``` just needs to go into ```src/vm/jvm/runtime/org/raku/nqp/runtime/Ops.java```.
@jstuder-gh sorry I've missed your request for a review back in 2018. I don't use Windows, but as far as I can see, adding the signals to ```sigWanted``` on the...
@jstuder-gh and another of your open PR that has conflicts after I merged the s/perl6/raku/ rename (#630). Again, it's hopefully easy to solve the conflicts, since the changes just need...
Just for the record: The mentioned issue for OpenJDK has been tagged as "affects version 17" and "solved for version 21". The issue also has two links to commits that...
I just tried on Debian 11 with ```jdk-17.0.8.1+1``` taken from https://adoptium.net/de/temurin/releases/ and didn't see an error building ```rakudo-j```. (There is a deprecation warning caused by ```-noverify``` being used, but that's...