RFR: 8377777: Improve logging when rejecting methods on the archive
Andrew Dinn
adinn at openjdk.org
Thu Feb 12 12:25:53 UTC 2026
On Thu, 12 Feb 2026 12:10:55 GMT, María Arias de Reyna Domínguez <duke at openjdk.org> wrote:
> Restored the check `if (resolved)` when printing if a CP entry is rejected or archived. If it is not resolved, we shouldn't even bother with it.
>
> Also, added log messages (mostly based on surrounding comments) on `ConstantPoolCache::can_archive_resolved_method` to add information about why a method gets rejected.
>
> All the log messages have the same format to be able to parse them easily:
>
> ` log.print("%s can't be archived because $REASON.",
> pool_holder->name()->as_C_string());`
@Delawen The new log messages apply to a variety of different assets, not just methods (e.g. your are avoiding spurious logging for CPCache entries". So, I think the title for the JIRA/PR should probably be "Improve logging when rejecting various types of asset from the archive".
-------------
PR Comment: https://git.openjdk.org/jdk/pull/29690#issuecomment-3890645766
More information about the hotspot-dev
mailing list