Blame SOURCES/java-1.8.0-openjdk-s390-java-opts.patch

9bf359
diff -up jdk8/common/autoconf/boot-jdk.m4.s390 jdk8/common/autoconf/boot-jdk.m4
9e49de
--- jdk8/common/autoconf/boot-jdk.m4.s390	2014-10-28 13:10:36.000000000 -0400
9e49de
+++ jdk8/common/autoconf/boot-jdk.m4	2015-01-09 15:49:45.443809100 -0500
9e49de
@@ -319,21 +319,12 @@ AC_DEFUN_ONCE([BOOTJDK_SETUP_BOOT_JDK_AR
9e49de
   AC_MSG_CHECKING([flags for boot jdk java command for big workloads])
9bf359
 
9e49de
   # Starting amount of heap memory.
9e49de
-  ADD_JVM_ARG_IF_OK([-Xms64M],boot_jdk_jvmargs_big,[$JAVA])
9e49de
+  ADD_JVM_ARG_IF_OK([-Xms256M],boot_jdk_jvmargs_big,[$JAVA])
9e49de
 
9e49de
   # Maximum amount of heap memory.
9e49de
   # Maximum stack size.
9e49de
-  if test "x$BUILD_NUM_BITS" = x32; then
9e49de
-    JVM_MAX_HEAP=1100M
9e49de
+    JVM_MAX_HEAP=768M
9e49de
     STACK_SIZE=768
9e49de
-  else
9e49de
-    # Running Javac on a JVM on a 64-bit machine, takes more space since 64-bit
9e49de
-    # pointers are used. Apparently, we need to increase the heap and stack
9e49de
-    # space for the jvm. More specifically, when running javac to build huge
9e49de
-    # jdk batch
9e49de
-    JVM_MAX_HEAP=1600M
9e49de
-    STACK_SIZE=1536
9e49de
-  fi
9e49de
   ADD_JVM_ARG_IF_OK([-Xmx$JVM_MAX_HEAP],boot_jdk_jvmargs_big,[$JAVA])
9e49de
   ADD_JVM_ARG_IF_OK([-XX:ThreadStackSize=$STACK_SIZE],boot_jdk_jvmargs_big,[$JAVA])
9e49de
   ADD_JVM_ARG_IF_OK([-XX:PermSize=32m],boot_jdk_jvmargs_big,[$JAVA])