Dan Horák
Dan Horák
You can reproduce the s390x behaviour by adding `--param=inline-min-speedup=2 --param=max-inline-insns-auto=80` to your compiler flags. This will enable the same level of aggressive inlining as gcc does on s390x by default....
If access to a s390x system would be useful, please let me know (sharkcz at fedoraproject.org).
s390x is the nickname for the modern 64-bit mainframes (and "s390" is the 32-bit variant going back to the S/360). The main difference to eg. i686/x86_64 is that s390/s390x is...
per https://src.fedoraproject.org/rpms/openexr/c/b278b7e1e53dd9b7fd783f8df5491dff37563500?branch=rawhide there were some issues even earlier (issue #876), but the ones reported here are the only remaining ones.
@cary-ilm, if you haven't seen my email reply yet, then check your spam box too, please.
Using the "zdev" (https://github.com/ibm-s390-linux/s390-tools/tree/master/zdev) mechanism it is possible to separate udev and networking configs. It works even now (on any recent Fedora and RHEL >= 8) , but it's still...
yes, I mean for desktops like XFCE
I believe the issue is/was intermittent, the test passes in the last builds in koji and in my local builds. Because `ppc64le` != `ppc64el`, so the test is actually enabled....
But as I said, the test passes, so no need to disable it in the build.
The intention is to use this issue to track the work required and keep the various teams working on it in sync.