Y. S. Ramakrishna
Y. S. Ramakrishna
Would be great to get some feedback also from either @shipilev or @rkennke . Thanks!
Code pipeline testing revealed a further scenario when `active_generation()` was used outside of what should have been a gc session (temporal) scope. I'll revert this to a draft until I...
A case of flickering of active_generation() was identified, and found to be benign. An assert now checks for this situation. The code has been made robust wrt the flickering.
> A case of flickering of active_generation() was identified, and found to be benign. An assert now checks for this situation. The code has been made robust wrt the flickering....
Publishing the draft for feedback. Still needs a few cleanups. Not too happy with the minutiae of the mechanics that need to be better abstracted.
In https://bugs.openjdk.org/browse/JDK-8328278, you state: > But the Serial GC computes tenuring threshold and prints new age table both after per GC. It causes the method `AgeTable::print_on` prints the wrong tenuring...
Where you state above that: > Then the message we print, Age table with threshold 12, is strange, because the age table we then print has 14 rows of non-zero...
> Hopefully, with the example above, you agree this is a problem? Thank you for the examples, and the explanation, Guoxiong and Albert. I agree that it would seem useful...
> Left a few minor coding suggestings. On a higher level, it's not clear to me when and which threads should use `gc_generation` or `active_generation`. I gather that active_generation is...