I'd suggest that we consider removing the VM flag UseMemSetInBOT. This is a dangerous flag to use as it will cause the VM to potentially crash on Sparc T4 (and later). There's currently a big warning printed when this is enabled by the user, but still, I don't see why anyone would want to ever enable this.
JDK-8039042 the name of this flag is slightly misleading, as it's not only used to control how the block offset table is initialized, but also how the cardtable is initialized. So instead of having a VM flag named UseMemSetInBOT we should have an internal state called memset_is_thread_safe (or something similar) which can be used by all cases where the memset() semantics is of interest.