Add reachabilityFence, remove ExemptionMechanism.finalize

ReachabilityFence is taken from Java 9.

ExemptionMechanism.finalize was never useful, and is also being removed
upstream. It is unsafe in the presence of dead reference elimination.

Bug: 63934467
Bug: 28342794
Test: Build and boot AOSP
Change-Id: I91dc4d33b91175248f44783e3c868a4f1b1d2d0d
This commit is contained in:
Hans Boehm
2018-01-18 20:21:29 -08:00
parent 0fc9900802
commit 242b93b760

View File

@@ -56393,6 +56393,7 @@ package java.lang.ref {
method public boolean enqueue();
method public T get();
method public boolean isEnqueued();
method public static void reachabilityFence(java.lang.Object);
}
public class ReferenceQueue<T> {
@@ -69415,7 +69416,6 @@ package javax.crypto {
public class ExemptionMechanism {
ctor protected ExemptionMechanism(javax.crypto.ExemptionMechanismSpi, java.security.Provider, java.lang.String);
method protected void finalize();
method public final byte[] genExemptionBlob() throws javax.crypto.ExemptionMechanismException, java.lang.IllegalStateException;
method public final int genExemptionBlob(byte[]) throws javax.crypto.ExemptionMechanismException, java.lang.IllegalStateException, javax.crypto.ShortBufferException;
method public final int genExemptionBlob(byte[], int) throws javax.crypto.ExemptionMechanismException, java.lang.IllegalStateException, javax.crypto.ShortBufferException;