JDK-8047735 : Investigate replacing System.security field with a VolatileCallSite
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2014-06-20
  • Updated: 2018-05-02
Related Reports
Relates :  
JDK-6642881 - Improve performance of Class.getClassLoader()
Relates :  
JDK-8191053 - Provide a mechanism to make system's security manager immutable
Description
From related bug:

Not directly targeting the subject of this bug but on a related topic is the attached patch which replaces the System.security field with a VolatileCallSite. The patch is not working properly yet because of bootstrapping issues but the idea is that CallSite optimizations in the JIT compilers can constant fold the System.getSecurityManager() call. Combined with intrinsification of Class.getClassLoader() (or better moving the class loader field up into Java) we could constant fold two security related checks.
Comments
I believe this issue would be addressed by the fix for JDK-8191053. Marking as a related (not a duplicate) issue for now though.
02-05-2018
Added securitymanager-performance label, as this is a potential performance improvement.
07-07-2014
I don't know very much about this, except the idea has been moved from another bug.
23-06-2014