This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/54934] New: Invalid debug/ array bounds w/-fno-range-check and 32-bit target
- From: "jan.kratochvil at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 15 Oct 2012 13:22:49 +0000
- Subject: [Bug fortran/54934] New: Invalid debug/ array bounds w/-fno-range-check and 32-bit target
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54934
Bug #: 54934
Summary: Invalid debug/ array bounds w/-fno-range-check and
32-bit target
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jan.kratochvil@redhat.com
Target: i386-unknown-linux-gnu
Siddhesh implemented support for 64-bit array bounds:
[PATCH] Expand fortran array bounds sizes to LONGEST
http://sourceware.org/ml/gdb-patches/2012-08/msg00562.html
+ dimension foo(4294967296:4294967297)
+ dimension bar(-4294967297:-4294967296)
This requires -fno-range-check for gfortran to compile it at all.
It works for x86_64 target but it produces wrong debug info for i386 target.
FAIL: gcc (GCC) 4.8.0 20121015 (experimental)
Is this a bug or not? Should GDB support 64-bit Fortran array bounds?
Should such bounds require -fno-range-check?