This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PING] Enhance array types debug info. for Ada
- From: Pierre-Marie de Rodat <derodat at adacore dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 15 Dec 2014 17:21:07 +0100
- Subject: [PING] Enhance array types debug info. for Ada
- Authentication-results: sourceware.org; auth=none
- References: <5406D305 dot 1060905 at adacore dot com> <20141003091848 dot GN1986 at tucnak dot redhat dot com> <54339F77 dot 7050300 at adacore dot com> <20141007082926 dot GF1986 at tucnak dot redhat dot com> <54358AFA dot 5020201 at adacore dot com> <20141126174239 dot GL1669 at tucnak dot redhat dot com> <547C8941 dot 2080607 at adacore dot com> <20141201153729 dot GJ1892 at tucnak dot redhat dot com> <547C9A19 dot 8020008 at adacore dot com>
Ping for https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00058.html.
On 12/01/2014 05:40 PM, Pierre-Marie de Rodat wrote:
While I agree this might trigger compatibility issues with old
debuggers, I don't know what to do assuming this change is not
acceptable: should we add a kludge in add_scalar_info in order to force
unsignedness when generating debugging information for Fortran?
Here is a data point: I tried to debug gfortran.dg/array_function_2.f90
build with my patches compiler for x86_64-linux with a GDB from an old
GNAT Pro release (5.03a1, from 2005):
(gdb) b array_function_2.f90:24
(gdb) r
(gdb) ptype q_in
type = real*8 (0:-1,-6:-1)
With a recent GDB, I have instead:
(gdb) ptype q_in
type = real(kind=8) (0:*,-6:*)
Given that the only thing that my patches changed in the debug
information for this example is the encoding of the arrays' lower
bounds, everything looks fine, here.
--
Pierre-Marie de Rodat