After discussing this on hotspot-runtime-dev [1], the general opinion seems to be that it would be worthwhile to get rid of INCLUDE_NMT and make NMT unconditional. This affects minimal builds only. As pointed out in the mail thread, the overhead is very small and it would get rid of one configuration to build and test.
[1] https://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2022-January/053504.html Patch removes INCLUDE_NMT from hotspot, as well as dependent macros, as well as the associated build option. ------------- Commit messages: - remove INCLUDE_NMT and dependend code Changes: https://git.openjdk.java.net/jdk/pull/7213/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=7213&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8280583 Stats: 217 lines in 28 files changed: 10 ins; 192 del; 15 mod Patch: https://git.openjdk.java.net/jdk/pull/7213.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/7213/head:pull/7213 PR: https://git.openjdk.java.net/jdk/pull/7213
