This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fortran DW_TAG_module/DW_TAG_imported_{declaration,module} support, improved DW_TAG_common_block support
- From: Tobias Burnus <tobias dot burnus at physik dot fu-berlin dot de>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Jason Merrill <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org, Jan Kratochvil <jkratoch at redhat dot com>, Daniel Jacobowitz <dan at codesourcery dot com>
- Date: Thu, 21 Aug 2008 23:00:14 +0200
- Subject: Re: [PATCH] Fortran DW_TAG_module/DW_TAG_imported_{declaration,module} support, improved DW_TAG_common_block support
- References: <20080821191221.GA4737@physik.fu-berlin.de> <20080821195104.GM8107@sunsite.mff.cuni.cz>
On Thu, Aug 21, 2008 at 09:51:04PM +0200, Jakub Jelinek wrote:
> That sounds like an idb bug, IMHO the Dwarf3 standard is quite clear
[...]
> with ifort/idb and see whether you can see in the debugger all i, j, k, l
> values or just i and j inside of MAIN__? The right behavior is to be able
> to print them all.
It seems to be indeed a idb bug - I'll fill a bugreport.
> I hope gdb will implement this correctly...
Me too, hopefully it will be implemented in the not-too-far future.
Regarding your patch: It regtested successfully here
and the Fortran bits are OK for the trunk.
Thanks a lot for your patch!
Tobias
PS: I'm a bit surprised that I can set a breakpoint at a USE statement.
I assume that typing "next" implies a NOOP?