From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] sim: erc32/m32c/rl78: add sim_memory_map stub for gdb
Date: Mon, 1 Feb 2021 23:53:33 -0500 [thread overview]
Message-ID: <20210202045333.26065-1-vapier@gentoo.org> (raw)
In-Reply-To: <YBgVT1tz8XQ2IzlZ@vapier>
These ports don't use the common sim core, so they weren't providing
a sim_memory_map for gdb, so they failed to link with the new memory
map logic added for the sim. Add stubs to fix.
erc32/
* interf.c (sim_memory_map): Define.
m32c/
* gdb-if.c (sim_memory_map): Define.
rl78/
* gdb-if.c (sim_memory_map): Define.
---
sim/erc32/interf.c | 6 ++++++
sim/m32c/gdb-if.c | 6 ++++++
sim/rl78/gdb-if.c | 6 ++++++
3 files changed, 18 insertions(+)
diff --git a/sim/erc32/interf.c b/sim/erc32/interf.c
index 5dd464b0ce76..ca2e9faea217 100644
--- a/sim/erc32/interf.c
+++ b/sim/erc32/interf.c
@@ -465,6 +465,12 @@ sim_complete_command (SIM_DESC sd, const char *text, const char *word)
return NULL;
}
+char *
+sim_memory_map (SIM_DESC sd)
+{
+ return NULL;
+}
+
#if 0 /* FIXME: These shouldn't exist. */
int
diff --git a/sim/m32c/gdb-if.c b/sim/m32c/gdb-if.c
index 5ada0b0bc17e..92e447f17faa 100644
--- a/sim/m32c/gdb-if.c
+++ b/sim/m32c/gdb-if.c
@@ -707,6 +707,12 @@ sim_complete_command (SIM_DESC sd, const char *text, const char *word)
return NULL;
}
+char *
+sim_memory_map (SIM_DESC sd)
+{
+ return NULL;
+}
+
void
sim_info (SIM_DESC sd, int verbose)
{
diff --git a/sim/rl78/gdb-if.c b/sim/rl78/gdb-if.c
index 320db34f436a..56717917e552 100644
--- a/sim/rl78/gdb-if.c
+++ b/sim/rl78/gdb-if.c
@@ -603,3 +603,9 @@ sim_complete_command (SIM_DESC sd, const char *text, const char *word)
{
return NULL;
}
+
+char *
+sim_memory_map (SIM_DESC sd)
+{
+ return NULL;
+}
--
2.30.0
next prev parent reply other threads:[~2021-02-02 4:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 11:44 [PATCH 00/11] fix build warnings for rx simulator Andrew Burgess
2021-02-01 11:44 ` [PATCH 01/11] sim/rx: define sim_memory_map Andrew Burgess
2021-02-01 14:46 ` Mike Frysinger via Gdb-patches
2021-02-08 11:01 ` Andrew Burgess
2021-02-01 11:44 ` [PATCH 02/11] sim/rx: fix an issue where we try to modify a const string Andrew Burgess
2021-02-01 11:44 ` [PATCH 03/11] sim/rx: fill in missing 'void' for empty argument lists Andrew Burgess
2021-02-01 11:44 ` [PATCH 04/11] sim/rx: mark some functions as static Andrew Burgess
2021-02-01 11:44 ` [PATCH 05/11] sim/rx: delete an unused function Andrew Burgess
2021-02-01 11:44 ` [PATCH 06/11] sim/rx: use puts instead of printf in a few places Andrew Burgess
2021-02-01 14:49 ` Mike Frysinger via Gdb-patches
2021-02-08 10:58 ` Andrew Burgess
2021-02-01 11:44 ` [PATCH 07/11] sim/rx: move some variable declarations to the start of the block Andrew Burgess
2021-02-01 11:44 ` [PATCH 08/11] sim/rx: use PRIx64 in printf format string Andrew Burgess
2021-02-01 11:44 ` [PATCH 09/11] sim/rx: add some missing includes Andrew Burgess
2021-02-01 11:44 ` [PATCH 10/11] sim/rx: avoid pointer arithmetic on void * pointers Andrew Burgess
2021-02-01 11:44 ` [PATCH 11/11] sim/rx: enable build with warnings Andrew Burgess
2021-02-01 14:50 ` Mike Frysinger via Gdb-patches
2021-02-02 4:53 ` Mike Frysinger via Gdb-patches [this message]
2021-02-08 10:57 ` Andrew Burgess
2021-02-02 4:37 ` [PATCH 00/11] fix build warnings for rx simulator Mike Frysinger via Gdb-patches
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=20210202045333.26065-1-vapier@gentoo.org \
--to=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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