Initial state of gc_thread.mut_spin
 
            
            
            
            
                1 Oct
                
                    2013
                
            
            
                1 Oct
                
                '13
                
            
            
            
        
    
                12:11 p.m.
            
        Hi everyone, In new_gc_thread(), why is gc_thread.mut_spin initialized to the 'released' state instead of the 'acquired' state (as with gc_spin)? I think this is wrong for two reasons: 1. During the first GC (but not during subsequent GCs), gcWorkerThread() releases mut_spin but mut_spin is not 'acquired' at this point. 2. The initial state of mut_spin is inconsistent with the final state of mut_spin at the end of a GC (it is in the 'acquired' state then). So it seems to me that mut_spin should be initialized to the 'acquired' state, like gc_spin is. Doing so would address these two points. Does this change make sense?
        4413
        
      
          Age (days ago)
        
      
        4413
        
    
          Last active (days ago)
        
        
        
        0 comments
    
    
        
        1 participants
    
    
    
    
    
    
    
    
    participants (1)
- 
                 Patrick Palka Patrick Palka