From: Nick Roberts <nickrob@snap.net.nz>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [11/11] Fortran dynamic arrays support: Fortran array testcase
Date: Fri, 16 Nov 2007 04:18:00 -0000 [thread overview]
Message-ID: <18237.6654.136445.432895@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20071116032049.GL9885@host0.dyn.jankratochvil.net>
> Also found out GDB testsuite (or rather dejagnu) never find gcc-4.x gfortran
> as it is no longer called `g77'. One can workaround it by: ln -s `which
> gfortran` g77
I also discovered this after I had contributed a patch based on use of g77:
* varobj.c (c_name_of_child, c_value_of_child): Allow non-zero
offsets for languages like Fortran.
ISTR that the patch failed with an executable built using gfortran but I never
noticed because the testsuite never found it.
> I assume it is a dejagnu bug and its `find_g77' should find even `gfortran'.
I think that the debug info from gfortran may be less complete than that from
g77 and that gfortran developers have issues that they consider more important.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-11-16 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 3:21 Jan Kratochvil
2007-11-16 4:18 ` Nick Roberts [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18237.6654.136445.432895@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox