Thomas Stuefe

> The bar for acceptance for a brand new locking scheme with no fallback is extremely high and needs a lot of bake time and broad performance measurements, to watch...

Is jtreg 7 downward compatible? Can I use it to test older JDKs, if yes, down to which version? Thanks!

> > Is jtreg 7 downward compatible? Can I use it to test older JDKs, if yes, down to which version? > > Yes, down to JDK 11. > >...

I'm confused. How does adding EnsureCapacity in newString646_US fix the compiler warning mentioned in JBS?

> > I'm confused. How does adding EnsureCapacity in newString646_US fix the compiler warning mentioned in JBS? > > I think this is a bona-fide compiler static analyzer bug. GCC...

The problem in [JDK-8292054](https://bugs.openjdk.org/browse/JDK-8292054) is that the output appears more than once, right? The hotspot code warns exactly once per encountered signal change. So if someone changes SIGFPE, then SIGILL,...

I don't have time to review, just chiming in that I look forward to use RWL in NMT, to simplify the lockless MST.

> @tstuefe I have a memory of there being a lock like this in NMT, but it must have been removed. > There is a lock for queries. MST is...

Hmm, I get uncomfortable if APIs mix layers and try to be smart. As in this case, an API that claims to return CG mem limit but mixes in knowledge...

So, before we had: ``` os::physical_memory() |----------------------------------------- | | v v OSContainer::memory_limit_in_bytes() os::Linux::physical_memory() ``` Made sense if one thinks of the `os` layer as the arbiter that has to lie...