On Thu, 6 Jul 2023 05:18:01 GMT, Jean-Philippe Bempel <jpbem...@openjdk.org> wrote:
> Fix a small leak in constant pool merging during retransformation of a class. > If this class has a catch block with `Throwable`, the class `Throwable` is > pre-resolved in the constant pool, while all the other classes are in a > unresolved state. So the constant pool merging process was considering the > entry with pre-resolved class as different compared to the destination and > create a new entry. We now try to consider it as equal specially for > Methodref/Fieldref. src/hotspot/share/oops/constantPool.cpp line 1361: > 1359: int recur2 = cp2->uncached_klass_ref_index_at(index2); > 1360: bool match = compare_entry_to(recur1, cp2, recur2); > 1361: match |= is_unresolved_class_mismatch(recur1, cp2, recur2); This is changing the definition of a "match" such that in all cases an unresolved class entry is considered equal to a resolved class entry - but only for these Field and MethodRefs. I don't see how this connects back to the original problem. Nor do I see why this is alway a correct thing to do. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/14780#discussion_r1255064413
