RFR: 8354547: REDO: Force clients to explicitly pass mem_tag value, even if it is mtNone [v4]

Gerard Ziemski gziemski at openjdk.org
Thu Apr 17 12:57:27 UTC 2025


> Redo for a follow-up to https://github.com/openjdk/jdk/pull/21843. Here we are focusing on removing the mem tag paremeter with default value of mtNone, to force everyone to provide mem tag, if known.
> 
> I tried to fill in tag, when I was pretty certain that I had the right type.
> 
> At least one more follow-up will be needed after this, to change the remaining mtNone to valid values.
> 
> Testing: passes tier1 locally on my mac, Mach5 tier1-5 in progress

Gerard Ziemski has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains five additional commits since the last revision:

 - Merge remote-tracking branch 'upstream/master' into JDK-8354547
 - remove last default argument (found by Stefan)
 - fix build break
 - fix build break
 - redo

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/24634/files
  - new: https://git.openjdk.org/jdk/pull/24634/files/d5cea15d..07a3e5c9

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=24634&range=03
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=24634&range=02-03

  Stats: 11700 lines in 230 files changed: 9301 ins; 1557 del; 842 mod
  Patch: https://git.openjdk.org/jdk/pull/24634.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/24634/head:pull/24634

PR: https://git.openjdk.org/jdk/pull/24634


More information about the shenandoah-dev mailing list