[aarch64-port-dev ] RFR: merge up to jdk8-b111

[Andrew McDermott]

I experimented with a (b111) client/release build and ran the same tests.

This time there were no errors reported, nor were there any processes left
spinning.

  client/release/hotspot Test results: passed: 328; failed: 11

I'll rebase my changes as the tip has moved on -- there were some fixes for
SEGVs during the week -- and then report back.



On 3 December 2013 12:02, Andrew McDermott <andrew.mcdermott at linaro.org>wrote:

>
> Edward Nevill <edward.nevill at linaro.org> writes:
>
> > On Tue, 2013-12-03 at 07:14 +0000, Andrew McDermott wrote:
> >> Hi,
> >>
> >> The attached or referenced changesets merge the aarch64-port to
> >> jdk8-b111. I have built both client and server and tested as follows:
> >
> > Hi Andrew,
> >
> > Thanks for doing this. The changes look fine.
> >
> > It would be useful to know how your test results compare with the test
> > results before the merge. Are you seeing significantly more failures?
>
> Reporting results as I get them...
>
> This is for cross-compilation.
>
> b111:
>
>  run 1: hotspot/client/fastdebug Test results: passed: 320; failed: 11;
> error: 8
>  run 2: hotspot/client/fastdebug Test results: passed: 321; failed: 10;
> error: 8
>
> b110
>
>  run 1: hotspot/client/release   Test results: passed: 325; failed: 14
>  run 2: hotspot/client/release   Test results: passed: 325; failed: 14
>
> > Are you seeing the same problems with tests 'spinning'?
>
> Running with b111 (-conc:3 -agentvm) I'm left with 3 processes spinning
> and introspecting those a little...
>
>   $ jstack 4583
>
>     4583: Unable to open socket file: target process not responding or
> HotSpot VM not loaded
>
>   $ strace -f -p 4583
>
>     Process 4583 attached with 7 threads
>     [pid  4582] futex(0x7f974a6898, FUTEX_WAIT_PRIVATE, 0, NULL
> <unfinished ...>
>     [pid  4581] futex(0x7f900f1764, FUTEX_WAIT_PRIVATE, 1, NULL
> <unfinished ...>
>     [pid  4580] futex(0x7f900ef564, FUTEX_WAIT_PRIVATE, 1, NULL
> <unfinished ...>
>     [pid  4579] restart_syscall(<... resuming interrupted call ...>
> <unfinished ...>
>     [pid  4578] futex(0x7f9000d064, FUTEX_WAIT_PRIVATE, 13, NULL
> <unfinished ...>
>     [pid  4577] futex(0x7f967842c0, FUTEX_WAIT, 4578, NULL <unfinished ...>
>     [pid  4579] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection
> timed out)
>     [pid  4579] futex(0x7f900e5230, FUTEX_WAKE_PRIVATE, 1) = 0
>     [pid  4579] futex(0x7f900e5264, FUTEX_WAIT_BITSET_PRIVATE, 1, {6666,
> 20080160}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
>     [pid  4579] futex(0x7f900e5230, FUTEX_WAKE_PRIVATE, 1) = 0
>     ... the 'Connection timed out' repeats ...
>
> I do _not_ see this behaviour with b110.
>
> And I repeated the exercise twice to avoid a sample size of 1...
>
> HTH,
> Andy.
>