We're currently using a fixed address space range for the mark stack space, both in terms of it's base address and it's size. This isn't really needed, we could just as well let os::reserve_memory() pick and address range for us and only reserve ZMarkStackSpaceLimit bytes, instead of 1TB.
            
- 
        
            
            
    
    Per Liden (Inactive) 
- 
        
            
            
    
    Per Liden (Inactive) 
- Votes:
- 
                                0 Vote for this issue
- Watchers:
- 
                                
                                
                            2 Start watching this issue
- Created:
- Updated:
- Resolved:
 P4
  P4