RFR: 8223347: Integration of Vector API (Incubator) [v4]
Ekaterina Pavlova
github.com+69653380+katyapav at openjdk.java.net
Wed Oct 14 00:50:25 UTC 2020
On Wed, 14 Oct 2020 00:34:04 GMT, Sandhya Viswanathan <sviswanathan at openjdk.org> wrote:
>> There are several gc tests crashed in panama-vector tier3 testing which seems are not observed in openjdk repo.
>> The crashes look like:
>> # assert(oopDesc::is_oop(obj)) failed: not an oop: 0xfffffffffffffff1
>> #
>> # JRE version: Java(TM) SE Runtime Environment (16.0+3) (fastdebug build 16-panama+3-216)
>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 16-panama+3-216, mixed mode, sharing, tiered, compressed oops,
>> g1 gc, linux-amd64) # Problematic frame:
>> # V [libjvm.so+0xd8ef94] HandleArea::allocate_handle(oop)+0x144
>>
>> and the issue is actually tracked by JDK-8233199.
>>
>> This issue needs to be at least analyzed before integrating Vector API.
>
> @katyapav Is the failure observed on vector-unstable branch of panama-vector?
> The code in this pull request is from vector-unstable branch.
> The bug report https://bugs.openjdk.java.net/browse/JDK-8233199 refers to repo-valhalla and not
> panama-vector:vector-unstable. @PaulSandoz is doing final testing of the pull request today before integration tomorrow
> hopefully.
@sviswa7 you are right, the failure is observed on vector-unstable branch of panama-vector.
I referred to JDK-8233199 because it seems both panama-vector and valhalla-repo have the same issue/crash.
@PaulSandoz also mentioned that panama-vector was not in sync with master and this is perhaps the issue is in
vector-unstable. He said that he tested the PR separately and didn't observe this issue in the PR.
-------------
PR: https://git.openjdk.java.net/jdk/pull/367
More information about the build-dev
mailing list