< prev index next >

src/share/vm/gc/g1/heapRegion.hpp

Print this page
rev 10868 : [mq]: 8153170-card-live-data-does-handle-eager-reclaim

@@ -122,11 +122,11 @@
   HeapWord* volatile _top;
   HeapWord* volatile _scan_top;
  protected:
   G1BlockOffsetTablePart _bot_part;
   Mutex _par_alloc_lock;
-  volatile unsigned _gc_time_stamp;
+  volatile uint _gc_time_stamp;
   // When we need to retire an allocation region, while other threads
   // are also concurrently trying to allocate into it, we typically
   // allocate a dummy object at the end of the region to ensure that
   // no more allocations can take place in it. However, sometimes we
   // want to know where the end of the last "real" object we allocated

@@ -172,11 +172,11 @@
   void mangle_unused_area_complete() PRODUCT_RETURN;
 
   HeapWord* scan_top() const;
   void record_timestamp();
   void reset_gc_time_stamp() { _gc_time_stamp = 0; }
-  unsigned get_gc_time_stamp() { return _gc_time_stamp; }
+  uint get_gc_time_stamp() { return _gc_time_stamp; }
   void record_retained_region();
 
   // See the comment above in the declaration of _pre_dummy_top for an
   // explanation of what it is.
   void set_pre_dummy_top(HeapWord* pre_dummy_top) {
< prev index next >