Suppress error warning in HotSpot backports
aph at redhat.com
Tue Mar 18 19:19:31 UTC 2014
On 03/18/2014 06:48 PM, Volker Simonis wrote:
> On Tue, Mar 18, 2014 at 7:24 PM, Andrew Haley <aph at redhat.com> wrote:
>> My thought is that tools like Netbeans, the Java build itself, etc,
>> are covered with -XX:MaxPermSize usages. These are needed, and people
>> aren't going to want to remove them, and neither are they going to
>> want their screen full of warnings. Would you?
> But that's exactly the point - with HS25 they aren’t needed because
> there is no PermGen any more and the VM can now freely load classes
> unless you run out of physical memory (or set MaxMetaspaceSize which
> is 2^64/2^32 by default).
> So if people upgrade to Java 8 they will need to remove this option or
> live with the warning.
But this is Java 7.
>>> And you may have noticed, that the hsx-project
>>> will be dissolved
>>> after jdk8 has been released (which should be actually today:)
>> Sure, I know, but ... why does that matter?
> Because there will be no place any more, where you can stabilize a
> specific HS version - at least not in the OpenJDK forests. Every Java
> 8 update will have its own HS version which is a clone of the HS25 in
> 8u-dev at some point in time.
> And there will be just one HS version for Java 9 (in jdk9/hs/hotspot).
> So if you'd like to downport a new HS version from 9 to 8 youll need
> to clone jdk9/hs/hotspot and stabilize that clone. But there’s
> currently neither a project nor a repository for such a task in the
> OpenJDK. The same applies if you'd like to downport a HS from 8 to 7 -
> you'd need to clone jdk8u/hotspot and stabilize that for 7. But again,
> there's no infrastructure for that any more - that was previously done
> in the various hsx repositories (i.e. hsx/hsx24, hsx//hsx25, ..). But
> they will be made read-only after the Java 8 release.
Oh, I see. I had no intention of using HSX for this, so it hadn't
occurred to me that it might be a problem.
More information about the hotspot-dev