RFR: 8344883: Do not use mtNone if we know the tag type [v2]

Gerard Ziemski gziemski at openjdk.org
Tue Apr 1 20:36:21 UTC 2025


On Fri, 28 Mar 2025 08:25:08 GMT, Stefan Karlsson <stefank at openjdk.org> wrote:

>> Gerard Ziemski has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   work
>
> I went over the patch and added suggestions for places where I think you're using the wrong tag, or where I think it is obvious that there's a better tag than mtNone. I've also suggested removal of the now redundant 'executable' argument, which I want to see as little of as possible given that it is a wart on the memory reservation APIs (IMHO).

@stefank After changing various `mtNone` tags to `mtTest` we know are seeing build failures:


#  Internal Error (/Users/runner/work/jdk/jdk/src/hotspot/share/nmt/virtualMemoryTracker.cpp:427), pid=79835, tid=8707
#  assert(reserved_rgn->mem_tag() == mtNone) failed: Overwrite memory tag (should be mtNone, is: "Test")


I would like to revert to the last passing commit [40cb438](https://github.com/openjdk/jdk/pull/24282/commits/40cb4384f17ad63c1374ea785f76e415a44eb426) and re-do this step in a follow-up.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/24282#issuecomment-2770608945


More information about the shenandoah-dev mailing list