archive/jdk
1
0
Fork 0
mirror of https://github.com/openjdk/jdk.git synced 2025-08-27 14:54:52 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

8228630: Remove always true parameter to NoSafepointVerifier

Browse source 
Also remove NoGCVerifier since NoSafepointVerifier covers GC checking when not already at a safepoint and is a stronger check.

Reviewed-by: kbarrett, dholmes
This commit is contained in:
Coleen Phillimore 2019-07-31 06:54:50 -04:00
parent 9ad5641ce5
commit ab9aab646b
11 changed files with 69 additions and 226 deletions
Download patch file Download diff file Expand all files Collapse all files

9
src/hotspot/share/runtime/thread.hpp
View file

@ -371,14 +371,15 @@ class Thread: public ThreadShadow {
private:
// debug support for checking if code does allow safepoints or not
// GC points in the VM can happen because of allocation, invoking a VM operation, or blocking on
// Debug support for checking if code allows safepoints or not.
// Safepoints in the VM can happen because of allocation, invoking a VM operation, or blocking on
// mutex, or blocking on an object synchronizer (Java locking).
// If !allow_safepoint(), then an assertion failure will happen in any of the above cases
// If _no_safepoint_count is non-zero, then an assertion failure will happen in any of
// the above cases.
//
// The class NoSafepointVerifier is used to set this counter.
//
NOT_PRODUCT(int _allow_safepoint_count;) // If 0, thread allow a safepoint to happen
NOT_PRODUCT(int _no_safepoint_count;) // If 0, thread allow a safepoint to happen
// Used by SkipGCALot class.
NOT_PRODUCT(bool _skip_gcalot;) // Should we elide gc-a-lot?