Suppress error warning in HotSpot backports

[Volker Simonis]

On Thu, Mar 20, 2014 at 1:09 AM, Andrew Hughes <gnu.andrew at redhat.com> wrote:
> ----- Original Message -----
>> On Wed, Mar 19, 2014 at 9:52 AM, Andrew Dinn <adinn at redhat.com> wrote:
>> > On 19/03/14 06:13, Volker Simonis wrote:
>> >> On Tuesday, March 18, 2014, Andrew Haley <aph at redhat.com> wrote:
>> >>> But this is Java 7.
>> >>
>> >>
>> >> Yes, but with HS25 which makes  it behave exactly like Java 8 in this
>> >> respect!
>> >
>> > The JVM in use for our AArch64 JDK7 is the one we built for JDK8. So,
>> > strictly, it is derived from the jdk8 tree, not the HS25 tree. That
>> > probably explains most clearly why it behaves like jdk8 :-)
>> >
>>
>> That's no difference.
>>
>> The flow of HS changes until the jdk8 release was:
>>
>> hsx/hotspot-{gc,rt,comp,emb} -> hsx/hotspot-main -> hsx/hsx25 -> jdk8
>>
>> After the release it probably will be:
>>
>> hsx/hotspot-main -> jdk8u-dev -> jdk8uXX
>>
>> The current contents of hsx/hotspot-main/hotspot, hsx/hsx25/hotspot
>> and jdk8/hotspot are all equal and contain HS 25.0-b70.
>>
>
> Hmm.. but I thought jdk8 would *always* be hs25 now. This seems to suggest
> that jdk8 is always getting the latest HotSpot development (i.e. same as 9 etc.)
>

You're right. The current plan is that jdk8 remains on hs25. But the
hsx repositories as well. They'll be only used for collecting jdk8
fixes. The current HS development happens in jdk9/hs-{comp,gc,runtime}
and there's no plan to downport that to hsx (i.e. the hsx project has
been disconnected)

>> Regards,
>> Volker
>>
>> > regards,
>> >
>> >
>> > Andrew Dinn
>> > -----------
>> >
>>
>
> --
> Andrew :)
>
> Free Java Software Engineer
> Red Hat, Inc. (http://www.redhat.com)
>
> PGP Key: 248BDC07 (https://keys.indymedia.org/)
> Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07
>