From: Carl Love <cel@us.ibm.com>
To: gdb-patches@sourceware.org,
will schmidt <will_schmidt@vnet.ibm.com>,
cel@us.ibm.com, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: [PATCH] Add PowerPC support to gdb.cp/call-method-register.cc
Date: Wed, 15 Jun 2022 10:40:08 -0700 [thread overview]
Message-ID: <97038d9f783fc6b65a6a4570f262f2409c6da2af.camel@us.ibm.com> (raw)
GDB maintainers:
This path adds the needed define ASM_REG for PowerPC to the test
program test program gdb.cp/call-method-register.cc. It was tested on
a Power 10 system with no regression failures.
Please let me know if this patch is acceptable for mainline.
Carl Love
--------------------------------------------------------------
Add PowerPC support to gdb.cp/call-method-register.cc
This patch adds the needed define ASM_REG for PowerPC.
The patch was run on a Power 10 system. The gdb Summary for the run lists
2 expected passes, no unexpected failures or untested testcases.
Please let me know if this patch is acceptable for mainline.
Carl Love
---
gdb/testsuite/gdb.cp/call-method-register.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/testsuite/gdb.cp/call-method-register.cc b/gdb/testsuite/gdb.cp/call-method-register.cc
index 06e9e53f988..d60fee03701 100644
--- a/gdb/testsuite/gdb.cp/call-method-register.cc
+++ b/gdb/testsuite/gdb.cp/call-method-register.cc
@@ -19,6 +19,8 @@
# define ASM_REG "rax"
#elif defined __i386__
# define ASM_REG "eax"
+#elif defined __powerpc64__
+# define ASM_REG "r9"
#else
# error "port me"
#endif
--
2.31.1
next reply other threads:[~2022-06-15 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:40 Carl Love [this message]
2022-06-30 15:13 ` [Ping] " Carl Love
2022-07-12 10:39 ` Ulrich Weigand
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=97038d9f783fc6b65a6a4570f262f2409c6da2af.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=will_schmidt@vnet.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).