From: Sergei Trofimovich <slyfox@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Sergei Trofimovich <siarheit@google.com>
Subject: [PATCH] gdb: fix IA64 build failure of linux-nat
Date: Tue, 19 May 2020 22:27:10 +0100 [thread overview]
Message-ID: <20200519212710.1417100-1-slyfox@gentoo.org> (raw)
From: Sergei Trofimovich <siarheit@google.com>
On IA64 built failed as:
```
ia64-linux-nat.c:352:29: error: 'gdbarch_num_regs' was not declared in this scope
352 | if (regno < 0 || regno >= gdbarch_num_regs (gdbarch))
| ^~~~~~~~~~~~~~~~
```
The fix includes "gdbarch.h" header where symbol is declared.
* gdb/ia64-linux-nat.c: include "gdbarch.h" to declare used
'gdbarch_num_regs'.
Signed-off-by: Sergei Trofimovich <siarheit@google.com>
---
gdb/ChangeLog | 5 +++++
gdb/ia64-linux-nat.c | 1 +
2 files changed, 6 insertions(+)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index ac0beef5ad..0d921da325 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2020-05-19 Sergei Trofimovich <siarheit@google.com>
+
+ * gdb/ia64-linux-nat.c: include "gdbarch.h" to declare used
+ 'gdbarch_num_regs'.
+
2020-05-19 Simon Marchi <simon.marchi@efficios.com>
* dwarf2/read.c (quirk_rust_enum): Allocate enough fields.
diff --git a/gdb/ia64-linux-nat.c b/gdb/ia64-linux-nat.c
index 8f36ea78e7..b532e7a51c 100644
--- a/gdb/ia64-linux-nat.c
+++ b/gdb/ia64-linux-nat.c
@@ -21,6 +21,7 @@
#include "defs.h"
#include "inferior.h"
#include "target.h"
+#include "gdbarch.h"
#include "gdbcore.h"
#include "regcache.h"
#include "ia64-tdep.h"
--
2.26.2
next reply other threads:[~2020-05-19 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:27 Sergei Trofimovich [this message]
2020-05-19 22:00 ` Kevin Buettner
2020-08-16 8:45 ` Sergei Trofimovich
2020-08-16 21:51 ` Simon Marchi
2020-08-17 8:54 ` Tom de Vries
2020-08-17 8:21 ` Simon Marchi
2020-08-17 18:59 ` Sergei Trofimovich
2020-08-18 8:46 ` Tom de Vries
2020-08-17 20:57 ` Sergei Trofimovich
2020-08-17 21:04 ` Simon Marchi
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=20200519212710.1417100-1-slyfox@gentoo.org \
--to=slyfox@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=siarheit@google.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