JDK-8238371 : ObjectSynchronizer::om_alloc() does not have to be public
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 15
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2020-02-01
  • Updated: 2020-11-11
  • Resolved: 2020-11-11
Related Reports
Duplicate :  
JDK-8253064 - monitor list simplifications and getting rid of TSM
Relates :  
JDK-8235795 - replace monitor list mux{Acquire,Release}(&gListLock) with spin locks
Description
Coleen raised a possible RFE in her review of:

JDK-8235795 replace monitor list mux{Acquire,Release}(&gListLock) with spin locks 

>  The function om_malloc() and many of these are 'public' in ObjectSynchronizer when they're only called within.  As a new RFE, can you make them private (or even static private if possible)? 
 
s/om_malloc()/om_alloc()/

Definitely makes sense to make more stuff private and, if possible,
static private. This fix (8235795) includes a bit of that, but
there's more room for improvement.
Comments
JDK-8253064 has been integrated. Closing this bug as a duplicate.
11-11-2020
Erik and Dan's work on this bug: JDK-8253064 monitor list simplifications and getting rid of TSM will delete ObjectSynchronizer::om_alloc() so this bug can be closed as a duplicate if/when JDK-8253064 gets integrated.
05-11-2020