> On 4 May 2017, at 17:58, Michael McMahon wrote:
>
> Hi Vyom,
>
> As discussed, I think there are still some issues including on 32 bit Linux
> and since we don't
> have too many of those machines left to debug with, it's probably best to
> back out the original
> change, and go back to the
Hi Vyom,
As discussed, I think there are still some issues including on 32 bit
Linux and since we don't
have too many of those machines left to debug with, it's probably best
to back out the original
change, and go back to the original webrev. We can then review an
updated version which takes
Hi All,
please find the latest
webrev(http://cr.openjdk.java.net/~vtewari/8179602/webrev0.1/index.html)
which fixed the Mac OS issued as well.
Michael as we we discussed off line, i incorporated the changes
suggested by you,
Thanks,
Vyom
On Thursday 04 May 2017 03:11 PM, Michael McMahon
Hi Vyom,
I notice this doesn't seem to fix the Mac OS problem.
We may have to file a separate issue for that.
- Michael
On 04/05/2017, 09:50, Vyom Tewari wrote:
Hi All,
Please review the below change.
Webrev: http://cr.openjdk.java.net/~vtewari/8179602/webrev0.0/index.html
Bugid: https://b
ge-
> From: net-dev [mailto:net-dev-boun...@openjdk.java.net] On Behalf Of
> Vyom Tewari
> Sent: Donnerstag, 4. Mai 2017 10:50
> To: net-dev
> Subject: RFR 8179602: Fix for JDK-8165437 is broken on 32-bit Linux
>
> Hi All,
>
> Please review the below change.
>
&g
Hi All,
Please review the below change.
Webrev: http://cr.openjdk.java.net/~vtewari/8179602/webrev0.0/index.html
Bugid: https://bugs.openjdk.java.net/browse/JDK-8179602
This issue is because of side effect of "JDK-8165437" where we are using
"JVM_NanoTime" which returns a 64 bit jlong and re
