From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: e500-regs.exp: fix little-endian 'print' patterns
Date: Mon, 14 Jun 2004 21:44:00 -0000 [thread overview]
Message-ID: <vt2brjl24ud.fsf@zenia.home> (raw)
Without this patch, all the 'print ev*' tests fail when the test
program is compiled with -mlittle. With the patch, they all pass.
Tested on i686-pc-linux-gnu host with the following targets:
powerpc-sim/-mlittle
powerpc-sim/-mbig
2004-06-14 Jim Blandy <jimb@redhat.com>
* gdb.arch/e500-regs.exp: Fix up 'print' pattern for the little-
endian case.
Index: gdb/testsuite/gdb.arch/e500-regs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/e500-regs.exp,v
retrieving revision 1.1
diff -c -p -r1.1 e500-regs.exp
*** gdb/testsuite/gdb.arch/e500-regs.exp 17 Mar 2003 20:06:16 -0000 1.1
--- gdb/testsuite/gdb.arch/e500-regs.exp 14 Jun 2004 21:40:43 -0000
*************** for {set i 0} {$i < 32} {incr i 1} {
*** 112,118 ****
if {$endianness == "big"} {
set decimal_vector ".uint64 = 4294967297, v2_float = .1.*e-45, 1.*e-45., v2_int32 = .1, 1., v4_int16 = .0, 1, 0, 1., v8_int8 = ..000.000.000.001.000.000.000.001.."
} else {
! set decimal_vector ".uint64 = 0x0000000100000001, v2_float = .1.*e-45, 1.*e-45., v2_int32 = .1, 1., v4_int16 = .1, 0, 1, 0., v8_int8 = ..001.000.000.000.001.000.000.000.001.000.000.000.001.000.000.."
}
for {set i 0} {$i < 32} {incr i 1} {
--- 112,118 ----
if {$endianness == "big"} {
set decimal_vector ".uint64 = 4294967297, v2_float = .1.*e-45, 1.*e-45., v2_int32 = .1, 1., v4_int16 = .0, 1, 0, 1., v8_int8 = ..000.000.000.001.000.000.000.001.."
} else {
! set decimal_vector ".uint64 = 4294967297, v2_float = .1.*e-45, 1.*e-45., v2_int32 = .1, 1., v4_int16 = .1, 0, 1, 0., v8_int8 = ..001.000.000.000.001.000.000.."
}
for {set i 0} {$i < 32} {incr i 1} {
next reply other threads:[~2004-06-14 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 21:44 Jim Blandy [this message]
2004-06-15 0:15 Michael Elizabeth Chastain
2004-06-15 18:17 ` Jim Blandy
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=vt2brjl24ud.fsf@zenia.home \
--to=jimb@redhat.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