RFR: 8163014: Mysterious/wrong value for "long" frame local variable on 64-bit

[Vladimir Kozlov]

Are you talking about next one?:

"Fix for JDK-8163014 broke Aarch64 build"
https://bugs.openjdk.java.net/browse/JDK-8166433

This one is not in hs-comp yet. I asked our gatekeeper to do sync from hs/ to hs-comp/.

Vladimir

On 9/26/16 10:56 AM, Andrew Haley wrote:
> On 26/09/16 18:49, Vladimir Kozlov wrote:
>> On 9/26/16 10:32 AM, Andrew Dinn wrote:
>>> On 26/09/16 16:20, Andrew Haley wrote:
>>>> On 22/09/16 10:14, Andrew Dinn wrote:
>>>>> Yes, I will push a fix to the hs tree.
>>>>
>>>> I'm still getting a failure in hs-comp.
>>>
>>> That will probably be because the patch went into hs and is not yet in
>>> hs-comp.
>>
>> It was pushed into hs-comp on Tue Sep 20 22:01:16 UTC 2016
>>
>> http://mail.openjdk.java.net/pipermail/jdk9-hs-comp-changes/2016-September/002246.html
>
> It wasn't:
>
> aph at arm64:~/hs-comp/hotspot$ hg pull
> pulling from ssh://hg.openjdk.java.net/jdk9/hs-comp/hotspot
> searching for changes
> no changes found
>
> aph at arm64:~/hs-comp/hotspot$ hg up
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
>
> aph at arm64:~/hs-comp/hotspot$ hg log src/cpu/aarch64/vm/interp_masm_aarch64.cpp  | head
> changeset:   11999:6c2a44eb27ac
> parent:      11942:a5f5a75e03ed
> user:        mockner
> date:        Tue Sep 13 11:04:29 2016 -0400
> summary:     8163014: Mysterious/wrong value for "long" frame local variable on 64-bit
>
> In other words, the new bug is there but not the fix for it.
>
> Andrew.
>