From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-54473-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 30431 invoked by alias); 11 Mar 2008 09:39:31 -0000
Received: (qmail 30423 invoked by uid 22791); 11 Mar 2008 09:39:30 -0000
X-Spam-Check-By: sourceware.org
Received: from host0.dyn.jankratochvil.net (HELO host0.dyn.jankratochvil.net) (89.250.240.59)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Mar 2008 09:38:55 +0000
Received: from host0.dyn.jankratochvil.net (localhost [127.0.0.1]) 	by host0.dyn.jankratochvil.net (8.14.2/8.14.1) with ESMTP id m2B9coZO017105; 	Tue, 11 Mar 2008 10:38:50 +0100
Received: (from jkratoch@localhost) 	by host0.dyn.jankratochvil.net (8.14.2/8.14.2/Submit) id m2B9cnte017104; 	Tue, 11 Mar 2008 10:38:49 +0100
Date: Tue, 11 Mar 2008 09:39:00 -0000
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Markus Deuling <deuling@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [6/6] Fortran dynamic arrays #2: Fortran array testcase
Message-ID: <20080311093849.GA16853@host0.dyn.jankratochvil.net>
References: <20071123234439.GG23460@host0.dyn.jankratochvil.net> <47D6478B.9000605@de.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47D6478B.9000605@de.ibm.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-03/txt/msg00115.txt.bz2

On Tue, 11 Mar 2008 09:49:15 +0100, Markus Deuling wrote:
...
> I also saw cases when gfortran emitted wrong or incomplete debug data but it gets
> better with 4.3.

The Fortran dynamic arrays debug info fix got committed for 4.3 by Jakub Jelink:
	http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22244


> Just a small comment to your testcase:
>
> +if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug f77 quiet}] != "" } {
> +    untested "Couldn't compile ${srcfile}"
> +    return -1
> +}
>
> I'm not able to compile your .f90 testcase with f77. What I did is to invoke gfortran instead, hoping
> 4.3 gets better :-)
>
> +if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug compiler=gfortran quiet}] != "" } {
> +    untested "Couldn't compile ${srcfile}"
> +    return -1
> +}

While it is correct it is in fact more a general problem of all of the upstream
Fortran testcases as AFAIK `g77' binary/link is just no longer present in GCC.
Using now a workaround in:
	http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/gdb/devel/gdb.spec
	cd $the_build_tree_root
	# g77 executable is no longer present in Fedora gcc-4.x+.
	g77="`which gfortran 2>/dev/null || true`"
	test -z "$g77" || ln -s "$g77" ./g77

Also the whole Fortran dynamic arrays patchset no longer applies well so it was
forward-ported for 6.8pre in between.  But only in its merged form:
	http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/gdb/devel/gdb-6.8-bz377541-fortran-dynamic-arrays.patch


Regards,
Jan