-
Bug
-
Resolution: Fixed
-
P4
-
11
-
b23
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8207305 | 12 | Volker Simonis | P4 | Resolved | Fixed | b03 |
JDK-8207514 | 11.0.2 | Volker Simonis | P4 | Resolved | Fixed | b01 |
JDK-8207625 | 11.0.1 | Volker Simonis | P4 | Resolved | Fixed | b02 |
The test runtime/ElfDecoder/TestElfDirectRead.java test intentionally disables caching of Elf sections during symbol lookup with WhiteBox.disableElfSectionCache(). On platforms which do not use function descriptors [1] instead of plain function pointers this slows down the lookup just a little bit, because all the symbols from an Elf file are still read consecutively after one 'fseek()' call. But on platforms with function descriptors like ppc64 big-endian, we get two 'fseek()' calls for each symbol read from the Elf file because reading the function descriptor table is nested inside the loop which reads the symbols. This really trashes the I/O system and considerable slows down the test, so we need an extra long timeout setting.
[1] https://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html#FUNC-DES
[1] https://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html#FUNC-DES
- backported by
-
JDK-8207305 [test] runtime/ElfDecoder/TestElfDirectRead.java requires longer timeout on ppc64
-
- Resolved
-
-
JDK-8207514 [test] runtime/ElfDecoder/TestElfDirectRead.java requires longer timeout on ppc64
-
- Resolved
-
-
JDK-8207625 [test] runtime/ElfDecoder/TestElfDirectRead.java requires longer timeout on ppc64
-
- Resolved
-