This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb/gdb-7.11-branch] testsuite: Fix false Fortran regressions with recent gcc
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Sun, 14 Feb 2016 03:52:50 -0500
- Subject: [binutils-gdb/gdb-7.11-branch] testsuite: Fix false Fortran regressions with recent gcc
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT 46e42194d8d2585b6860b1267c2b3e24ba9c589c ***
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.11-branch
Commit: 46e42194d8d2585b6860b1267c2b3e24ba9c589c
testsuite: Fix false Fortran regressions with recent gcc
gcc-4.9.2-6.fc21.x86_64 -> gcc-5.3.1-2.fc23.x86_64
-PASS: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
+FAIL: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
-PASS: gdb.fortran/vla-history.exp: print vla1 allocated
+FAIL: gdb.fortran/vla-history.exp: print vla1 allocated
-PASS: gdb.fortran/vla-history.exp: print $2
+FAIL: gdb.fortran/vla-history.exp: print $2
-PASS: gdb.fortran/vla-value.exp: print undefined pvla
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla
-PASS: gdb.fortran/vla-value.exp: print non-associated &pvla
+FAIL: gdb.fortran/vla-value.exp: print non-associated &pvla
-PASS: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
These issues get fixed (or removed if no longer applicable) by attached patch.
It is based on Googled:
http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html#5
When a pointer is declared its status is undefined, and cannot be
safely queried with the associated intrinsic.
-> nullify(VARNAME)
+
https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268786
ALLOCATE is not supposed to initialize the array.
-> Remove checks like an initial print is: \\( *0, *0, *0...\\)
These regressions remain:
-PASS: gdb.fortran/library-module.exp: print var_i in lib
+FAIL: gdb.fortran/library-module.exp: print var_i in lib
-PASS: gdb.fortran/library-module.exp: print var_i in main
+FAIL: gdb.fortran/library-module.exp: print var_i in main
I believe it is more a GDB bug (in a code contributed by me), filed:
gdb.fortran/library-module.exp false regression on GCC upgrade
https://sourceware.org/bugzilla/show_bug.cgi?id=19635
gdb/testsuite/ChangeLog
2016-02-14 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix compatibility with recent gfortran-5.3.1.
* gdb.fortran/vla-history.exp (print vla1 allocated)
(print vla2 allocated, print $2, print $3): Remove
(print $4): Rename to ...
(print $2): ... here.
(print $9): Rename to ...
(print $5): ... here.
(print $10): Rename to ...
(print $6): ... here.
* gdb.fortran/vla.f90: Add pvla initialization.
- Follow-Ups:
- Failures on RHEL-s390x-m64, branch gdb-7.11-branch
- Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch gdb-7.11-branch
- Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.11-branch
- Failures on Fedora-s390x-m64, branch gdb-7.11-branch
- Failures on AIX-POWER7-plain, branch gdb-7.11-branch
- Failures on Debian-s390x-native-gdbserver-m64, branch gdb-7.11-branch
- Failures on Debian-s390x-m64, branch gdb-7.11-branch
- Failures on Debian-s390x-native-extended-gdbserver-m64, branch gdb-7.11-branch
- Failures on Debian-x86_64-native-extended-gdbserver-m64, branch gdb-7.11-branch
- Failures on Fedora-ppc64be-cc-with-index, branch gdb-7.11-branch
- Failures on Debian-i686-native-extended-gdbserver, branch gdb-7.11-branch
- Failures on Fedora-ppc64be-native-gdbserver-m64, branch gdb-7.11-branch
- Failures on Fedora-ppc64be-native-extended-gdbserver-m64, branch gdb-7.11-branch
- Failures on Fedora-ppc64le-native-extended-gdbserver-m64, branch gdb-7.11-branch
- Failures on Fedora-ppc64le-cc-with-index, branch gdb-7.11-branch
- Failures on Fedora-ppc64le-native-gdbserver-m64, branch gdb-7.11-branch