- ppc-aix-port-dev - openjdk.org

RFR: 8221741 [AIX] Unexpected X11 bitmap fonts are loaded because of fontconfig.properties
by Ichiroh Takiguchi 02 Apr '19

02 Apr '19

Hello. Could you review the fix ? Bug: https://bugs.openjdk.java.net/browse/JDK-8221741 Change: https://cr.openjdk.java.net/~itakiguchi/8221741/webrev.00/ I'd like to obtain a sponsor for this issue. On AIX platform, fontconfig.properties file is used to pick up proper fonts. TrueType font settings are written by XLFD format on fontconfig.properties file. On current implementation, Java tries to load X11 bitmap fonts even if these are not used. This font load work is almost name as "xlsfonts -ll". It spends many CPU time and memories. Just font name format should be supported. To SAP representative, I have a question about copyright year on make/data/fontconfig/aix.fontconfig.properties. Please let me know how I should write down copyright year. Thanks, Ichiroh Takiguchi IBM Japan, Ltd.

3 2

RFR(S): 8220794: PPC64: Fix signal handler for SIGSEGV on branch to illegal address
by Gustavo Romero 26 Mar '19

26 Mar '19

Hi, Please, could I get reviews for the following change: bug : https://bugs.openjdk.java.net/browse/JDK-8220794 webrev: http://cr.openjdk.java.net/~gromero/8220794/v1/ It fixes the JVM signal handler on Linux / PPC64 when a SIGSEGV generated by a branch to an illegal/invalid address (not mapped address, address with no executable flags, etc) is caught by the JVM signal handler. Currently the signal handler does not handle that case correctly and the JVM crashes silently. That issue was reported by Goetz (SAP). Thanks for reporting the issue, Goetz. Thank you. Best regards, Gustavo

3 6

RFR(S): 8221175: Fix bad function case for controlled JVM crash on PPC64 big-endian
by Gustavo Romero 26 Mar '19

26 Mar '19

Hi, Please, could I get reviews for the following change? bug : https://bugs.openjdk.java.net/browse/JDK-8221175 webrev: http://cr.openjdk.java.net/~gromero/8221175/v1/ It fixes the way a function pointer is defined in order to call a bad function at address 0xF (controlled crash case 13) on PPC64 big-endian machines. On PPC64 big-endian compiler defaults to ABI ELFv1 which mandates function pointers to part of a function descriptor, at offset 0 [1]. Currently the SIGISEGV being generated by case 13 is incorrect because if a function descriptor is not use to call the bad function address the program segfaults before effectively calling the function, when trying to load the (bad) function pointer from offset 0 of base address 0xF, so before branching to the function. It does not affect PPC64 little-endian machines because by default ABI ELFv2 is used (instead of ABI ELFv1) and for that ABI no function descriptor is defined / employed. The fix consists in defining properly a function descriptor with a bad function at offset 0 (the following offset are no important in that case) and using that function descriptor to call the bad function, only on PPC64 big-endian machines. That issue was found when investigating the JDK-8220794 issue [2]. Thank you. Best regards, Gustavo [1] http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html#FUNC-DES [2] https://bugs.openjdk.java.net/browse/JDK-8220794

4 12

jdk-build on AIX with xlc16/ xlclang++ : issue with (ibm)demangle.hpp
by Baesken, Matthias 31 Jan '19

31 Jan '19

Hello, when attempting to compile jdk/jdk on AIX with the recently released xlc16 / xlclang++ , I run into an issue with the compilation of hotspot/os/aix/porting_aix.cpp . The error is caused by the inclusion of demangle.h in porting_aix.cpp which leads to this error message : #error "Please include ibmdemangle.h for xlclang++ to demangle symbol names." However the inclusion of 'ibmdemangle.h' fails with : /jdk/src/hotspot/os/aix/porting_aix.cpp:39:10: fatal error: 'ibmdemangle.h' file not found #include <ibmdemangle.h> Does anyone know where 'ibmdemangle.h' should come from ? I cannot find it in the compiler installation of xlc16 . And it is also not in /usr/include . My current workaround is to disable the C++ name demangling in porting_aix.cpp . Thanks, Matthias

1 0

Fwd: Re: RFR: 8212794 IBM-964 and IBM-29626C are required for AIX default charset
by Ichiroh Takiguchi 29 Jan '19

29 Jan '19

Hello. Martin Buchholz suggested me via bugs.openjdk.java.net, I should not touch non AIX side. So I rewrote another code. Could you review the fix again ? Bug: https://bugs.openjdk.java.net/browse/JDK-8212794 Change: https://cr.openjdk.java.net/~itakiguchi/8212794/webrev.01/ I don't want to touch non AIX side code, but I need to rename 3 files to avoid compilation issue. IBM33722.java -> IBM33722.java.template IBM964.java -> IBM964.java.template SimpleEUCEncoder.java -> SimpleEUCEncoder.java.template Thanks, Ichiroh Takiguchi IBM Japan, Ltd. -------- Original Message -------- Subject: Re: RFR: 8212794 IBM-964 and IBM-29626C are required for AIX default charset Date: 2018-11-08 20:13 From: Volker Simonis <volker.simonis(a)gmail.com> To: Ichiroh Takiguchi <takiguc(a)linux.vnet.ibm.com> Cc: Java Core Libs <core-libs-dev(a)openjdk.java.net>, ppc-aix-port-dev(a)openjdk.java.net, "SHEN, XUEMING" <xueming.shen(a)oracle.com>, Alan Bateman <Alan.Bateman(a)oracle.com> Hi Ichiroh, sorry, but unfortunately, this change is way beyond my level of expertise :) You should try to get a review from Sherman or Alan. Regards, Volker On Fri, Oct 26, 2018 at 3:33 PM Ichiroh Takiguchi <takiguc(a)linux.vnet.ibm.com> wrote: > > Hello. > > Could you review the fix ? > > Bug: https://bugs.openjdk.java.net/browse/JDK-8212794 > Change: https://cr.openjdk.java.net/~itakiguchi/8212794/webrev.00/ > > I'd like to obtain a sponsor for this issue. > > > IBM964 charset and IBM29626C charset are required for default charset > on AIX zh_TW and ja_JP locale. > OpenJDK already has IBM964, but it could not be configured for default > charset. > IBM29626C is new one. > (IBM33722 extends IBM29626C class) > > I knew IBM charsets would need to move to somewhere. > The discussion was started by "Adding new IBM extended charsets". [1] > But it's related default charset issue. > Please put them inside of OpenJDK. > > About IBM964, > Bhaktavatsal started the discussion [2]. > Sherman said that [3] > the new model (open/make/data/charetmapping), instead of hard-coding > the map > into the source code. > > This fix only has small sized hard-coded mapping, > IBM964/IBM29626C/IBM33722 refer other charsets conversion table > which are using the new model. > And class file is smaller then before. > Still I used SimpleEUCEncoder class because it's stable. > I think we may re-write it by IBM charsets renewal. > > Thanks, > Ichiroh Takiguchi > IBM Japan, Ltd. > > [1] > http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-July/054248.html > [2] > http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-May/053050.html > [3] > http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-May/053096.html >

7 35

RFR: 8207404: MulticastSocket tests failing on AIX
by Langer, Christoph 21 Jan '19

21 Jan '19

Hi, here is a fix for the MulticastSocket tests failing on AIX (in certain sceanrios): Webrev: http://cr.openjdk.java.net/~clanger/webrevs/8207404.0/ Bug: https://bugs.openjdk.java.net/browse/JDK-8207404 First of all, I "modernized" the testcases test/jdk/java/net/MulticastSocket/SetGetNetworkInterfaceTest.java and test/jdk/java/net/MulticastSocket/Test.java to make use of test/lib/jdk/test/lib/NetworkConfiguration.java which probes for the network configuration and returns lists of local interfaces or addresses for certain use cases. In NetworkConfiguration.java I made some cleanups and enhancements which will hopefully find some appreciation. These 3 tests will now also be executed with and without -Djava.net.preferIPv4Stack=true. The actual fixes are: test/jdk/java/net/MulticastSocket/JoinLeave.java: test/jdk/java/net/MulticastSocket/SetGetNetworkInterfaceTest.java: -> NetworkConfiguration.ip4MulticastInterfaces() will now, on AIX, in a scenario where IPv6 is available, filter out interfaces that only have IPv4 addresses (line 121ff in test/lib/jdk/test/lib/NetworkConfiguration.java) test/jdk/java/net/MulticastSocket/Test.java: -> The test for node local multicasting is only executed, when NetworkConfiguration::hasTestableIPv6Address is true. For AIX it'll be the case only if a "real" IPv6 address exists (on some interface) which is not loopback or wildcard. This is how it has already been for Solaris. For other operating systems, any IPv6 address on any interface is sufficient for running the test. The coding for the AIX/Solaris check can be found in line 66ff of test/lib/jdk/test/lib/NetworkConfiguration.java. As it is a test only fix, I request to do it in JDK12. Thanks & Best regards Christoph

3 8

RFR [XS] 8217233: Update build settings for AIX/xlc
by Baesken, Matthias 17 Jan '19

17 Jan '19

Hello, please review this small fix . It adds stack protection compile flags for xlc/AIX . See : https://www.ibm.com/support/knowledgecenter/SSGH2K_12.1.0/com.ibm.xlc121.ai… "Provides protection against malicious code or programming errors that overwrite or corrupt the stack." The patch will set the stack protection flags . ( Similar changes have been done for Linux : 8199552: Update to build scripts https://hg.openjdk.java.net/jdk-updates/jdk11u/rev/8b060cdf0251 Introduced stack protection compile flags for Linux/gcc ( -fstack-protector ) . ) Bug/webrev : https://bugs.openjdk.java.net/browse/JDK-8217233 http://cr.openjdk.java.net/~mbaesken/webrevs/8217233.0/ Thanks, Matthias

3 4

8207404: MulticastSocket tests failing on Aix
by Steve Groeger 15 Jan '19

15 Jan '19

Hi All, I have been having a look at this issue: https://bugs.openjdk.java.net/browse/JDK-8207404 which was raised by Goetz Lindenmaier. When I ran the tests on my AIX system I got the same results as Goetz listed in the issue. Looking at the failure I noticed that it was failing on a setsockopt call in the native code in the PlainDatagramSocketImpl.c file which returned a EADDRNOTAVAIL (Can't assign requested address) Looking at my network configuration using "ifconfig -a", I noticed that my interface "en0" which the test was trying to use did not have an inet6 address configured (see below - some addresses have been obfuscated with x's). en0: flags=1e084863,14c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN> inet 9.20.xx.xx netmask 0xffffff00 broadcast 9.20.xx.xxx tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1 configuring the IPV6 on my AIX box I then had a inet6 address configured for en0 en0: flags=1e084863,14c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN> inet 9.20.xx.xx netmask 0xffffff00 broadcast 9.20.xx.xxx inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1 with this configured the MulticastSocket tests all passed. Should these tests work without having IPV6 configured on the interface? Goetz, do you have IPV6 configured on the machine you were running these tests on? Thanks Steve Groeger IBM Runtime Technologies Hursley, UK Tel: (44) 1962 816911 Mobex: 279990 Mobile: 07718 517 129 Fax (44) 1962 816800 Lotus Notes: Steve Groeger/UK/IBM Internet: groeges(a)uk.ibm.com Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

6 15

Open ppc/s390/aix issues
by Lindenmaier, Goetz 09 Jan '19

09 Jan '19

Hi, We are now working on the ppc/s390/aix ports for quite some years. With the release of jdk11 we delivered a very comprehensive and well maintained port I think. For example, the jdk and hotspot jtreg tests can be run quite stable on these platforms. I filed bugs for all the remaining issues we see, at least in the test setup we run at SAP. Everybody is invited to join in and fix these few finally :) 8207404: MulticastSocket tests failing on Aix https://bugs.openjdk.java.net/browse/JDK-8207404 8030957: AIX: Implement OperatingSystemMXBean.getSystemCpuLoad() and .getProcessCpuLoad() on AIX https://bugs.openjdk.java.net/browse/JDK-8030957 8211769: Port Dtrace support to ppc. https://bugs.openjdk.java.net/browse/JDK-8211769 8211771: Port Dtrace support to s390x. https://bugs.openjdk.java.net/browse/JDK-8211771 8211767: jtreg: Some SA tests are failing on PPC64 https://bugs.openjdk.java.net/browse/JDK-8211767 8211844: [aix] ProcessBuilder: Piping between created processes does not work. https://bugs.openjdk.java.net/browse/JDK-8211844 8211847: [aix] java/lang/ProcessHandle/InfoTest.java fails: "reported cputime less than expected" https://bugs.openjdk.java.net/browse/JDK-8211847 8211854: [aix] java/net/ServerSocket/AcceptInheritHandle.java fais: read times out https://bugs.openjdk.java.net/browse/JDK-8211854 8211851: /java/nio/channels/AsynchronousSocketChannel/StressLoopback.java times out (aix) https://bugs.openjdk.java.net/browse/JDK-8211851 8211841: [aix] sun/nio/cs/OLD/TestIBMDB.java fails with compilation error https://bugs.openjdk.java.net/browse/JDK-8211841 Best regards, Goetz.

3 6

SAP discontinues active support of jdk7u on linuxppc64 and aixppc64
by Lindenmaier, Goetz 09 Jan '19

09 Jan '19

Hi, AS OpenJDK 7 is no longer relevant to SAP, we will no more actively support our port platforms linuxppc64 and aixppc64 in hg.openjdk.java.net/jdk7u/jdk7u. This means we will cancel our regular builds and tests of the repository. Nevertheless, in urgent cases we will still assist. Of course, we will continue our active support of linuxppc64 and aixppc64 in OpenJDK 8 and keep up our activities in the less recent versions. Best regards, Götz Lindenmaier

2 1