Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8082965 | emb-9 | Jesper Wilhelmsson | P3 | Resolved | Fixed | team |
Today GenCollectedHeap contains an array with room for ten generations, and there is plenty of code that is written in a very generic way to allow for this many generations. However, there is also plenty of code that assumes we only use two generations and any attempt to use more would fail with the current code. In practice we only use two generations and there are no reason to maintain the illusion that we could use more.
To simplify the code the array should be removed and we should be explicit in all code accessing the generations about which generation we actually are using.
To simplify the code the array should be removed and we should be explicit in all code accessing the generations about which generation we actually are using.
- backported by
-
JDK-8082965 REDO - Remove the generations array
-
- Resolved
-
- blocks
-
JDK-8057632 Remove auxiliary code used to handle the generations array
-
- Resolved
-
-
JDK-8072809 Further cleanups after Generation array removal: gen_process_roots and OopsInGenClosure::set_generation
-
- Closed
-
- clones
-
JDK-8055702 Remove the generations array
-
- Closed
-
- relates to
-
JDK-8075635 Remove GenerationSpec array
-
- Resolved
-
-
JDK-8076267 Remove n_gens()
-
- Resolved
-
(1 relates to)