RFR: 8168503 JEP 297: Unified arm32/arm64 Port

[Edward Nevill]

On Fri, 2016-12-02 at 15:28 -0500, Bob Vandette wrote:
> Please review the proposed changes to be integrated under JEP 297.
> 

Looks good. I have run it through JTreg on x86, arm32 and arm64 systems. Results below. The repo I used was the 'hs' repo.

On x86 I did two runs, original repo and patched with your webrev. For arm64 I did two runs, one the arm64 unified build (ie the webrev below) and one, the existing aarch64 build.

All builds were release builds.

For the jdk tests I used the options -k:\!headful\&\!intermittant\&\!randomness to suppress any tests requiring X11.

I will append these results to a comment in the issue and start running jcstress.

All the best,
Ed.

x86(original):

hotspot: passed: 1,337; failed: 5; error: 44 (0 fatal errors)*
langtools: passed: 3,757; failed: 5; error: 8 (0 fatal errors)
jdk: passed: 6,348; failed: 194; error: 11 (1 fatal error)

x86(patched):

hotspot: passed: 1,337; failed: 5; error: 44 (0 fatal errors)
langtools: passed: 3,757; failed: 5; error: 8 (0 fatal errors)
jdk: passed: 6,346; failed: 196; error: 10 (0 fatal errors)

arm32

hotspot: passed: 1,244; failed: 5; error: 44 (0 fatal errors)
langtools: passed: 3,761; failed: 1; error: 8 (0 fatal errors)
jdk: passed: 6,339; failed: 197; error: 11 (0 fatal errors)

aarch64

hotspot: passed: 1,325; failed: 9; error: 44 (0 fatal errors)
langtools: passed: 3,757; failed: 2; error: 8 (0 fatal errors)
jdk: passed: 6,389; failed: 155; error: 9 (0 fatal errors)

arm64

hotspot: passed: 1,327; failed: 7; error: 44 (0 fatal errors)
langtools: passed 3,760; failed: 1; error: 8 (0 fatal errors)
jdk: passed: 6,408; failed: 136; error: 9 (0 fatal errors)

* 'fatal' errors are those where the test failed with the message "A fatal error has been detected" in the .jtr file.