From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: Testsuite failure (mi-var-child-f.exp)
Date: Tue, 31 Oct 2006 20:31:00 -0000 [thread overview]
Message-ID: <20061031203059.GA4013@nevyn.them.org> (raw)
In-Reply-To: <17735.45334.494821.411911@kahikatea.snap.net.nz>
On Wed, Nov 01, 2006 at 09:24:54AM +1300, Nick Roberts wrote:
> > They won't tell you that; they're aware that gfortran's debug info is
> > mostly junk. Steven Bosscher has been working on it.
>
> It worked for g77, and I thought gfortran was a fork of that.
No, they're basically unrelated.
> Anyway are you saying there is little point in reporting it since
> there are many other problems with the debug info?
No, the opposite. There's a meta-bug in the GCC bugzilla tracking
debug info issues. If there isn't already one for array indexes, just
file a new one.
> Also how about my other point: Should the testuite find gfortran or is that
> a DajaGnu issue?
I don't know. It seems like testing gfortran would be more useful than
g77 nowadays.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-31 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 8:47 Nick Roberts
2006-10-31 8:53 ` Nick Roberts
2006-10-31 13:44 ` Daniel Jacobowitz
2006-10-31 20:29 ` Nick Roberts
2006-10-31 20:31 ` Daniel Jacobowitz [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=20061031203059.GA4013@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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