From: Peter Bergner <bergner@vnet.ibm.com>
To: gdb <gdb@sourceware.org>
Subject: [PATCH, COMMITTED] Fix PPC rfebb test case results
Date: Tue, 23 Jun 2015 18:44:00 -0000 [thread overview]
Message-ID: <1435085032.5416.48.camel@otta> (raw)
My gas patch in the URL below fixed a problem with the assembly and
disassembly of the rfebb instruction:
https://sourceware.org/ml/binutils/2015-06/msg00190.html
This patch updates the gdb test suite to match the new disassembly
behavior. Committed as obvious.
Peter
gdb/testsuite/
* gdb.arch/powerpc-power.exp <rfebb>: Fixup test results.
* gdb.arch/powerpc-power.s <rfebb>: Likewise.
diff --git a/gdb/testsuite/gdb.arch/powerpc-power.exp
b/gdb/testsuite/gdb.arch/powerpc-power.exp
index 15a59dd..96d623f 100644
--- a/gdb/testsuite/gdb.arch/powerpc-power.exp
+++ b/gdb/testsuite/gdb.arch/powerpc-power.exp
@@ -194,8 +194,8 @@ func_check +500 "treclaim. r24"
func_check +504 "trechkpt."
func_check +508 "tsuspend."
func_check +512 "tresume."
-func_check +516 "rfebb"
-func_check +520 "rfebb 1"
+func_check +516 "rfebb 0"
+func_check +520 "rfebb"
func_check +524 "bctar- 12,4\\*cr5\\+gt"
func_check +528 "bctarl- 4,4\\*cr1\\+so"
func_check +532 "bctar\\+ 12,4\\*cr3\\+lt"
diff --git a/gdb/testsuite/gdb.arch/powerpc-power.s
b/gdb/testsuite/gdb.arch/powerpc-power.s
index 335e35b..ed17b2e 100644
--- a/gdb/testsuite/gdb.arch/powerpc-power.s
+++ b/gdb/testsuite/gdb.arch/powerpc-power.s
@@ -147,7 +147,7 @@ func:
.long 0x7c0007dd /* <+504>: trechkpt. */
.long 0x7c0005dd /* <+508>: tsuspend. */
.long 0x7c2005dd /* <+512>: tresume. */
- .long 0x4c000124 /* <+516>: rfebb */
+ .long 0x4c000124 /* <+516>: rfebb 0 */
.long 0x4c000924 /* <+520>: rfebb 1 */
.long 0x4d950460 /* <+524>: bctar- 12,4*cr5+gt */
.long 0x4c870461 /* <+528>: bctarl- 4,4*cr1+so */
reply other threads:[~2015-06-23 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1435085032.5416.48.camel@otta \
--to=bergner@vnet.ibm.com \
--cc=gdb@sourceware.org \
/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