From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC/testsuite] Update "info float" output for i386
Date: Tue, 14 Jan 2003 04:15:00 -0000 [thread overview]
Message-ID: <20030114041526.GA1885@nevyn.them.org> (raw)
I'm still in testsuite maintenance mode, for a little while longer. I'm on
the home stretch for GCC 2.95.3 + stabs; as soon as I finish, I'll do my
monthly apt-get dist-upgrade, the default compiler on my Debian machine will
change to GCC 3.2 + DWARF-2, and I'll be right back where I started at
dozens of failures. But I'll have a tremendous sense of accomplishment!
Some time ago Mark Kettenis updated i387-tdep.c to use frame_register_read
for "info float". This changed the result of "info float" with no running
program; I think for the better, and so did he, if I recall rightly. Can
anyone think of a reason not to update the testsuite correspondingly, as
with the attached patch?
For reference, the old output was a zeroed register dump; the new is "The
program has no registers now." Which is quite entirely accurate.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-01-13 Daniel Jacobowitz <drow@mvista.com>
* gdb.base/default.exp (info float): Update expected output for
i386.
Index: gdb.base/default.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/default.exp,v
retrieving revision 1.14
diff -u -p -r1.14 default.exp
--- gdb.base/default.exp 18 Oct 2002 18:54:55 -0000 1.14
+++ gdb.base/default.exp 14 Jan 2003 04:10:46 -0000
@@ -1,5 +1,5 @@
# Copyright 1988, 1990, 1991, 1992, 1994, 1995, 1996, 1997, 1998, 1999,
-# 2000, 2001, 2002
+# 2000, 2001, 2002, 2003
# Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
@@ -325,7 +325,7 @@ if { [istarget "arm*-*-*"] || \
[istarget "strongarm*-*-*"] } then {
gdb_test "info float" "Software FPU type.*mask:.*flags:.*" "info float"
} elseif [istarget "i\[3456\]86-*-*"] then {
- gdb_test "info float" "R7:.*Status Word:.*Opcode:.*" "info float"
+ gdb_test "info float" "The program has no registers now." "info float"
} else {
gdb_test "info float" "No floating.point info available for this processor." "info float"
}
next reply other threads:[~2003-01-14 4:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 4:15 Daniel Jacobowitz [this message]
2003-01-14 5:52 ` Andrew Cagney
2003-01-14 5:54 ` Daniel Jacobowitz
2003-01-14 15:36 ` Andrew Cagney
2003-01-15 0:48 ` Mark Kettenis
2003-01-15 2:00 ` Daniel Jacobowitz
2003-01-15 14:48 ` Fernando Nasser
2003-01-15 22:22 ` Mark Kettenis
2003-01-14 7:41 Michael Elizabeth Chastain
2003-01-15 1:14 Michael Elizabeth Chastain
2003-01-15 23:26 ` Mark Kettenis
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=20030114041526.GA1885@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.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