P4
There are about 180 hotspot tests that still use ASM and there are no plans to rewrite them.
Currently, test/hotspot/jtreg/testlibrary/asm contains some modified asm sources. To reduce maintenance cost it makes sense to use current objectweb asm library for them.
The library might be build dependency and in this case we need to add it to jtreg classpath somehow.
Another way would be just to bundle ASM library with jtreg like we are doing for asmtools, junit or testng and treat it like those libraries.
I sanity verified that testing pass with standard asm library. Assuming that we don't know exact version of current asm and don't know about private modification, I think it is fine to replace it.
Currently, test/hotspot/jtreg/testlibrary/asm contains some modified asm sources. To reduce maintenance cost it makes sense to use current objectweb asm library for them.
The library might be build dependency and in this case we need to add it to jtreg classpath somehow.
Another way would be just to bundle ASM library with jtreg like we are doing for asmtools, junit or testng and treat it like those libraries.
I sanity verified that testing pass with standard asm library. Assuming that we don't know exact version of current asm and don't know about private modification, I think it is fine to replace it.