From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb@sourceware.org
Subject: New Fortran test failures
Date: Tue, 28 Feb 2006 02:54:00 -0000 [thread overview]
Message-ID: <20060227163318.GA20782@nevyn.them.org> (raw)
Hi Wu,
Have you run the GDB testsuite lately? I don't have before-and-after
results, but it looks like your recent Fortran patch caused extra
whitespace after printing certain Fortran types, which shows up as
failures in gdb.fortran/types.exp. I'm not sure why.
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2006-02-27 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 2:54 Daniel Jacobowitz [this message]
2006-02-28 14:04 ` Wu Zhou
2006-02-28 15:46 ` Daniel Jacobowitz
2006-03-01 1:39 ` Wu Zhou
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=20060227163318.GA20782@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=woodzltc@cn.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).