On 2016-06-28 06:30, David Holmes wrote:
Hi Erik,
This may coincide with the switch from the client VM to server VM on
32-bit Windows.
That is a very likely cause.
Fix looks fine to me.
Thanks! But after leaving work yesterday I thought some more on it and
didn't like my fix. It really was a bit of a hack. When doing a
bootcycle build, the jvm arguments should be based on the bits of the
target rather than the original bootjdk. If the host has a small amount
of memory, that should also affect the bootcycle build. Here is a new
webrev which solves it in a more correct way.
http://cr.openjdk.java.net/~erikj/8160285/webrev.top.02/
/Erik
