1berry/openjdk
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

8346737: GenShen: Generational memory pools should not report zero for maximum capacity

Browse Source 
Reviewed-by: kdnilsen, ysr
This commit is contained in:
William Kemper 2024-12-20 23:51:49 +00:00
parent d562d3c7a9
commit 249f141211
2 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/hotspot/share/gc/shenandoah/shenandoahMemoryPool.cpp
View File

@ -93,11 +93,6 @@ size_t ShenandoahGenerationalMemoryPool::used_in_bytes() {
return _generation->used();
}
size_t ShenandoahGenerationalMemoryPool::max_size() const {
return _generation->max_capacity();
}
ShenandoahYoungGenMemoryPool::ShenandoahYoungGenMemoryPool(ShenandoahHeap* heap) :
ShenandoahGenerationalMemoryPool(heap,
"Shenandoah Young Gen",

1
src/hotspot/share/gc/shenandoah/shenandoahMemoryPool.hpp
View File

@ -55,7 +55,6 @@ public:
explicit ShenandoahGenerationalMemoryPool(ShenandoahHeap* heap, const char* name, ShenandoahGeneration* generation);
MemoryUsage get_memory_usage() override;
size_t used_in_bytes() override;
size_t max_size() const override;
};
class ShenandoahYoungGenMemoryPool : public ShenandoahGenerationalMemoryPool {