Package: gfortran-9 Severity: serious Justification: Causes FTBFS -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi, I've recently uploaded libcgns 8.4.0-1~exp1 to experimental. All builds but ppc64el are ok. The ppc64el failure [0] occurs in the test suite (test cgread_f03), when a C va_arg function (src/cg_ftoc.c:cg_goto_f()) is called from Fortran code (src/tests/cgread_f03.F90:421). This function is called several times. Is is successful at first, then it fails badly because the corresponding hidden string length parameters[1] are equal to 0. This shouldn't happen because the related strings are literals: 'Zone_t', 'GridCoordinates_t', 'end'. [0] https://buildd.debian.org/status/fetch.php?pkg=libcgns&arch=ppc64el&ver=3.4.0-1%7Eexp1&stamp=1572269974&raw=0 [1] https://gcc.gnu.org/onlinedocs/gfortran/Argument-passing-conventions.html Further investigation shows that release 3.3.0-6 of libcgns FTBFS the very same way with GCC 8.3.0, while it succeeded with GCC 8.2.0 [2]. [2] https://buildd.debian.org/status/fetch.php?pkg=libcgns&arch=ppc64el&ver=3.3.0-6%2Bb2&stamp=1542797186&raw=0 I then ran a bisect on the GCC svn branch 'gcc-8-branch' and found out that the failure was introduced by the r269349 changeset [3]. [3] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=269349 This is a backport of the trunk r268992 changetset [4] introduced during GCC-9 development. [4] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=268992 At this point I don't know where to go. I'm setting severity = serious because this change now present into Debian/sid GCC-{7,8,9} makes libcgns FTBFS on ppc64el. Feel free to downgrade it if you think it appropriate. Any help appreciated. Many thanks in advance, _g. - -- System Information: Debian Release: buster/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl3AXBgACgkQ7+hsbH/+ z4O20Af/U24cwYYZ52fdUfa82GGT8lMP2YIeZiOl9fm9F+6T1d5BFhJAUVGxei9e 3L+kGECJoTYcX8i3Ou0yKhPtuYCDaJ3ceBl93bBW5/obO+epWr3XLAkG5sVcJDO4 pHUh32dqjEuXCz6CZfPVv5bARSZpT9CUxyo1d6ylikfqbXCE0Rw8qeSj8Q2+iOyJ xoLL9lZXLo9GnGvVz/O5+xtxulmF5F77uO+NmP6sr+7oqZydFb3j3f6//RTumpKs Bco0A3tPtP71eCJsO+KwremHZV7MAAkUO5GBdQP7IcVj6rISJE08kI/hEmnP89wi KcSoVYbi2Uax2lKqH/E57FqQlkkkHQ== =5u/M -----END PGP SIGNATURE-----