From: Stafford Horne <shorne@gmail.com>
To: gdb-patches@sourceware.org
Cc: openrisc@lists.librecores.org, Stafford Horne <shorne@gmail.com>
Subject: [PATCH v3 2/3] gdb: testsuite: Add or1k l.nop inscruction
Date: Thu, 22 Dec 2016 16:14:00 -0000 [thread overview]
Message-ID: <4c18cd33f9b932d40a7ffa67b772c17775d147f4.1482413820.git.shorne@gmail.com> (raw)
In-Reply-To: <cover.1482413820.git.shorne@gmail.com>
In-Reply-To: <cover.1482413820.git.shorne@gmail.com>
The test case requires adding a nop instruction. For or1k the
instruction is `l.nop`. This change uses the correct operation.
gdb/testsuite/ChangeLog:
2016-05-11 Stafford Horne <shorne@gmail.com>
* gdb.base/bp-permanent.c: Define nop of or1k.
---
gdb/testsuite/gdb.base/bp-permanent.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/testsuite/gdb.base/bp-permanent.c b/gdb/testsuite/gdb.base/bp-permanent.c
index 541a89b..7e17dc7 100644
--- a/gdb/testsuite/gdb.base/bp-permanent.c
+++ b/gdb/testsuite/gdb.base/bp-permanent.c
@@ -26,6 +26,8 @@
#if defined(__s390__) || defined(__s390x__)
#define NOP asm("nopr 0")
+#elif defined(__or1k__)
+#define NOP asm("l.nop")
#else
#define NOP asm("nop")
#endif
--
2.7.4
next prev parent reply other threads:[~2016-12-22 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 16:14 [PATCH v3 0/3] OpenRISC gdb port Stafford Horne
2016-12-22 16:14 ` Stafford Horne [this message]
2016-12-22 16:14 ` [PATCH v3 3/3] Add gdb for or1k build Stafford Horne
2016-12-22 16:14 ` [PATCH v3 1/3] gdb: Add OpenRISC or1k and or1knd target support Stafford Horne
2016-12-23 21:21 ` Luis Machado
2016-12-25 1:31 ` Stafford Horne
2016-12-26 16:10 ` Luis Machado
2016-12-27 13:20 ` Stafford Horne
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=4c18cd33f9b932d40a7ffa67b772c17775d147f4.1482413820.git.shorne@gmail.com \
--to=shorne@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=openrisc@lists.librecores.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