Enhance removed loads/substitutes in LSE.
LSE does load removal in the end in order to maintain the validity of
all the heap locations collected in the first pass. We should however
proactively retrieve a removed load's substitute as its value. This
simplifies the handling of substitutes by making sure the substitute
itself has no substitute. It also enables some additional optimizations
by using the true heap value for merging/same-value test, etc.
Test: run-test on host.
Change-Id: I26d97e7794d80a141ab02bf446dd07656f5cde1d
diff --git a/test/530-checker-lse/src/Main.java b/test/530-checker-lse/src/Main.java
index c4cc3b0..f6332b5 100644
--- a/test/530-checker-lse/src/Main.java
+++ b/test/530-checker-lse/src/Main.java
@@ -999,6 +999,24 @@
return res;
}
+ /// CHECK-START: void Main.testStoreSameValue() load_store_elimination (before)
+ /// CHECK: NewArray
+ /// CHECK: ArrayGet
+ /// CHECK: ArraySet
+
+ /// CHECK-START: void Main.testStoreSameValue() load_store_elimination (after)
+ /// CHECK: NewArray
+ /// CHECK-NOT: ArrayGet
+ /// CHECK-NOT: ArraySet
+ private static void testStoreSameValue() {
+ Object[] array = new Object[2];
+ sArray = array;
+ Object obj = array[0];
+ array[1] = obj; // store the same value as the defaut value.
+ }
+
+ static Object[] sArray;
+
static void assertIntEquals(int result, int expected) {
if (expected != result) {
throw new Error("Expected: " + expected + ", found: " + result);