RFR(XS): 8147482: Zero build fails after 8144953
volker.simonis at gmail.com
Sat Jan 16 10:43:50 UTC 2016
I totally agree and I'd like to but there have been complaints before when
we pushed ppc64 or AIX only changes to shared directories.
So until we don't get a general and clear agreement on this topic I'd like
to ask you to be so kind and do the push.
Thank you and best regards,
On Friday, January 15, 2016, Coleen Phillimore <coleen.phillimore at oracle.com>
> On 1/15/16 2:20 PM, Volker Simonis wrote:
>> Hi Severin,
>> the change looks good.
>> Unfortunately I can't sponsor it because it is in shared code.
> Actually, since it's in Zero only, I think it would be okay to push
> directly. It's not technically in the cpu/zero/vm directory but these
> files are only used for Zero.
> Alas, we don't test Zero with JPRT. If we start doing this, a. it
> wouldn't break so often and b. we'd have to sponsor just to make sure it
> doesn't break and prevent other integration jobs from going through.
>> On Fri, Jan 15, 2016 at 7:46 PM, Severin Gehwolf <sgehwolf at redhat.com>
>>> Could somebody please review and sponsor this trivial change to
>>> bytecodeInterpreter.cpp. It fixes a Zero-only build problem.
>>> Bug: https://bugs.openjdk.java.net/browse/JDK-8147482
>>> Zero builds fine in release/fastdebug/slowdebug variants after this.
More information about the hotspot-dev