There's already a NoSafepointVerifier check at the same place.

The comments say that NoAllocVerifier only make sense at safepoints:

-// Note: this only makes sense at safepoints (otherwise, other threads may
-// allocate concurrently.)

Given there aren't any uses of this to help understand this comment, this code should be removed.