| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-2195930 | 7 | John Coomes | P3 | Closed | Fixed | b102 | 
| JDK-2197791 | 6u23 | John Coomes | P3 | Resolved | Fixed | b01 | 
| JDK-2199691 | 6u22m | John Coomes | P3 | Resolved | Fixed | b01 | 
| JDK-2197505 | 6u21p | John Coomes | P3 | Resolved | Fixed | b03 | 
                    Code that uses TaskQueue to hold stealable tasks has to allow for the fixed-size TaskQueue to overflow.  This is often done using a separate per-thread overflow stack.  Maintaining the TaskQueue and overflow stack separately is tedious and error prone; a TaskQueue with built-in overflow handling is needed.
            
- backported by
- 
                    JDK-2197505 simplify TaskQueue overflow handling -           
- Resolved
 
-         
- 
                    JDK-2197791 simplify TaskQueue overflow handling -           
- Resolved
 
-         
- 
                    JDK-2199691 simplify TaskQueue overflow handling -           
- Resolved
 
-         
- 
                    JDK-2195930 simplify TaskQueue overflow handling -           
- Closed
 
-         
- relates to
- 
                    JDK-6962947 shared TaskQueue statistics -           
- Resolved
 
-         
- 
                    JDK-6966222 G1: simplify TaskQueue overflow handling -           
- Closed
 
-         
- 
                    JDK-6961798 GC stack draining code could enable more stealing -           
- Closed
 
-         
             (2 relates to)