On Tue, 23 Aug 2022 07:59:32 GMT, Fei Yang wrote:
> So I give it a second try with fastdebug build on my unmatched board [1], I
> see the error has changed into [2]. Is there anything I missed? Thanks.
I don't know why I did not get this assertion error on my end before. I fixed
the issue and
On Mon, 22 Aug 2022 11:32:54 GMT, Sacha Coppey wrote:
> Sorry for the delay, but all the JVMCI tests now pass.
So I give it a second try with fastdebug build on my unmatched board [1], I see
the error has changed into [2].
Is there anything I missed? Thanks.
[1]
$ make run-test-only
TEST="./t
On Mon, 22 Aug 2022 16:57:41 GMT, Sacha Coppey wrote:
>> src/jdk.internal.vm.ci/share/classes/jdk.vm.ci.riscv64/src/jdk/vm/ci/riscv64/RISCV64Kind.java
>> line 54:
>>
>>> 52: V256_QWORD(32, QWORD),
>>> 53: V256_SINGLE(32, SINGLE),
>>> 54: V256_DOUBLE(32, DOUBLE);
>>
>> I see some ve
On Mon, 22 Aug 2022 14:05:49 GMT, Fei Yang wrote:
>> Sacha Coppey has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Add space in switch
>
> src/jdk.internal.vm.ci/share/classes/jdk.vm.ci.riscv64/src/jdk/vm/ci/riscv64/RISCV64Kind.java
> li
On Wed, 27 Jul 2022 11:25:22 GMT, Sacha Coppey wrote:
>> This patch adds a partial JVMCI implementation for RISC-V, to allow using
>> the GraalVM Native Image RISC-V LLVM backend, which does not use JVMCI for
>> code emission.
>> It creates the jdk.vm.ci.riscv64 and jdk.vm.ci.hotspot.riscv64 pa
On Wed, 27 Jul 2022 11:25:22 GMT, Sacha Coppey wrote:
>> This patch adds a partial JVMCI implementation for RISC-V, to allow using
>> the GraalVM Native Image RISC-V LLVM backend, which does not use JVMCI for
>> code emission.
>> It creates the jdk.vm.ci.riscv64 and jdk.vm.ci.hotspot.riscv64 pa
