Summary: It introduces the necessary memory pools for G1.
Reviewed-by: mchung, ysr

Summary: ScavengeALot now causes an incremental (but possibly partially young, in the G1 sense) collection. Some such collections may be abandoned on account of MMU specs. Band-aided a native leak associated with abandoned pauses, as well as an MMU tracker overflow related to frequent scavenge events in the face of a large MMU denominator interval; the latter is protected by a product flag that defaults to false.
Reviewed-by: tonyp

Summary: Protected stats dump with a new develop flag; other than for the dump, reconciled product and non-product behaviour in face of the error.
Reviewed-by: tonyp

Summary: Added instrumentation and (temporary) assert in non-product mode; clipped the value when found out-of-bounds in product mode. Fix of original issue will follow collection of data from this instrumentation.
Reviewed-by: jcoomes, tonyp

Summary: Use CollectorPolicy information instead of MaxNewSize
Reviewed-by: ysr, jcoomes

Summary: The type in the NEW_C_HEAP_ARRRY and FREE_C_HEAP_ARRAY calls in the buffer allocation code was changed from void* to char as the size argument had already been mulitipled by the byte size of an object pointer.
Reviewed-by: ysr, tonyp

Summary: Allow iteration over the shared spaces when using CDS, repealing previous proscription. Deferred further required CDS-related cleanups of perm gen to CR 6897789.
Reviewed-by: phh, jmasa

Summary: Incorrect code was being generated for the store operation in the null case of the aastore bytecode template. The bad code was generated by the store_heap_oop routine which takes a Register as its second argument. Passing NULL_WORD (0) as the second argument causes the value to be converted to Register(0), which is rax. Thus the generated store was "mov (dst), $rax" instead of "mov (dst), $0x0". Changed calls to store_heap_oop that pass NULL_WORD as the second argument to a new routine store_heap_oop_null.
Reviewed-by: kvn, twisti

Summary: Restore old behaviour wrt HeapDumpPath; first dump goes to <file>, <n>th dump goes to <file>.<n-1>, with default value of <file> the same as before.
Reviewed-by: alanb, jcoomes, tonyp

Summary: The problem occurs with negative numbers, as the 32-bit input values are sign extended into the 64-bit registers.
Reviewed-by: kvn

Summary: The fix addresses two memory leaks in G1 code: (1) _evac_failure_scan_stack - a resource object allocated on the C heap was not freed; (2) RSHashTable were linked into deleted list which was only cleared at full GC.
Reviewed-by: tonyp, iveresov

Summary: Update the HS17 build number to 04
Reviewed-by: jcoomes

Reviewed-by: tonyp, ysr

Summary: Implement scalar replaced objects debug info dump in SA.
Reviewed-by: twisti

Summary: Fix the shadowing and incorrect macro usages
Reviewed-by: coleenp

Summary: Removed the assert: UseSerialGC is not necessarily always set when serial gc is being used.
Reviewed-by: jcoomes, jmasa, tonyp

Summary: correctly raise exceptions, support safe bitwise "raw" conversions, fix bugs revealed by VerifyMethodHandles, remove dead code, improve debugging support
Reviewed-by: never, twisti

6889757: G1: enable card mark elision for initializing writes from compiled code (ReduceInitialCardMarks)
Summary: Defer the (compiler-elided) card-mark upon a slow-path allocation until after the store  and before the next subsequent safepoint; G1 now answers yes to can_elide_tlab_write_barriers().
Reviewed-by: jcoomes, kvn, never

Reviewed-by: kvn, twisti

Summary: Restore original null checks.
Reviewed-by: never, cfang

Summary: Use -y zip option to preserve symbolic links.
Reviewed-by: never, jcoomes, kamg

Reviewed-by: jrose, kvn, cfang, twisti

Summary: PhiNode::Ideal() should return TOP for Phi node with no users.
Reviewed-by: never, jrose

Summary: Restore the original code: uint i = _hi_degree.
Reviewed-by: never, jrose

Reviewed-by: twisti, jrose, kvn

Reviewed-by: never
Contributed-by: gbenson@redhat.com

Summary: Update the HS17 build number to 03
Reviewed-by: jcoomes

Summary: What the title says. We don't use SIMPLE_STACK any more.
Reviewed-by: ysr