Mercurial > jdk8-mips64-public / file comparison
comparison: common/autoconf/boot-jdk.m4
common/autoconf/boot-jdk.m4
- changeset 2222
- 7129b977c4af
- parent 1580
- f398f28e3112
- child 2316
- 64a3eeabf6e5
equal
deleted
inserted
replaced
| 2221:888144400d97 | 2222:7129b977c4af |
|---|---|
| 332 ADD_JVM_ARG_IF_OK([-Xms64M],boot_jdk_jvmargs_big,[$JAVA]) | 332 ADD_JVM_ARG_IF_OK([-Xms64M],boot_jdk_jvmargs_big,[$JAVA]) |
| 333 | 333 |
| 334 # Maximum amount of heap memory. | 334 # Maximum amount of heap memory. |
| 335 # Maximum stack size. | 335 # Maximum stack size. |
| 336 if test "x$BOOT_JDK_BITS" = x32; then | 336 if test "x$BOOT_JDK_BITS" = x32; then |
| 337 JVM_MAX_HEAP=1100M | 337 JVM_MAX_HEAP=768M |
| 338 STACK_SIZE=768 | 338 STACK_SIZE=768 |
| 339 else | 339 else |
| 340 # Running Javac on a JVM on a 64-bit machine, takes more space since 64-bit | 340 # Running Javac on a JVM on a 64-bit machine, takes more space since 64-bit |
| 341 # pointers are used. Apparently, we need to increase the heap and stack | 341 # pointers are used. Apparently, we need to increase the heap and stack |
| 342 # space for the jvm. More specifically, when running javac to build huge | 342 # space for the jvm. More specifically, when running javac to build huge |
