Mercurial > hg > truffle
comparison src/share/vm/gc_implementation/parNew/parNewGeneration.cpp @ 12030:330dfb0476f4
8022800: Use specific generations rather than generation iteration
Reviewed-by: jmasa, ehelin
author | brutisso |
---|---|
date | Wed, 14 Aug 2013 09:02:32 +0200 |
parents | f2110083203d |
children | 190899198332 |
comparison
equal
deleted
inserted
replaced
12009:39127bb12d32 | 12030:330dfb0476f4 |
---|---|
925 int active_workers = | 925 int active_workers = |
926 AdaptiveSizePolicy::calc_active_workers(workers->total_workers(), | 926 AdaptiveSizePolicy::calc_active_workers(workers->total_workers(), |
927 workers->active_workers(), | 927 workers->active_workers(), |
928 Threads::number_of_non_daemon_threads()); | 928 Threads::number_of_non_daemon_threads()); |
929 workers->set_active_workers(active_workers); | 929 workers->set_active_workers(active_workers); |
930 _next_gen = gch->next_gen(this); | |
931 assert(_next_gen != NULL, | |
932 "This must be the youngest gen, and not the only gen"); | |
933 assert(gch->n_gens() == 2, | 930 assert(gch->n_gens() == 2, |
934 "Par collection currently only works with single older gen."); | 931 "Par collection currently only works with single older gen."); |
932 _next_gen = gch->next_gen(this); | |
935 // Do we have to avoid promotion_undo? | 933 // Do we have to avoid promotion_undo? |
936 if (gch->collector_policy()->is_concurrent_mark_sweep_policy()) { | 934 if (gch->collector_policy()->is_concurrent_mark_sweep_policy()) { |
937 set_avoid_promotion_undo(true); | 935 set_avoid_promotion_undo(true); |
938 } | 936 } |
939 | 937 |