On Fri, 5 Jul 2024 17:44:14 GMT, Andrew Haley <a...@openjdk.org> wrote:
> I also had problems with javac running out of heap space, which was very odd. > I fixed it with this: > > ``` > diff --git a/make/autoconf/boot-jdk.m4 b/make/autoconf/boot-jdk.m4 > index 8d272c28ad5..617ccfd8fff 100644 > --- a/make/autoconf/boot-jdk.m4 > +++ b/make/autoconf/boot-jdk.m4 > @@ -470,7 +470,7 @@ AC_DEFUN_ONCE([BOOTJDK_SETUP_BOOT_JDK_ARGUMENTS], > # Maximum amount of heap memory. > JVM_HEAP_LIMIT_32="768" > # Running a 64 bit JVM allows for and requires a bigger heap > - JVM_HEAP_LIMIT_64="1600" > + JVM_HEAP_LIMIT_64="6400" > ``` For the command to run the tests, I use `make test TEST=org.openjdk.bench.jdk.incubator.vector.operation.Float" MICRO="FORK=1;ITER=10;WARMUP_ITER=10;JAVA_OPTIONS=-XX:+UnlockExperimentalVMOptions -XX:UseSVE=1 -XX:+EnableVectorSupport -XX:+UseVectorStubs"`. I just copy and run Double/Float benchmark tests (without copying other tests under `org.openjdk.bench.jdk.incubator.vector.operation`), in which way I think it will not have this OOM issue. ------------- PR Comment: https://git.openjdk.org/jdk/pull/18605#issuecomment-2213280630
