From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Fix build breakage in rs6000-aix-tdep.c
Date: Thu, 16 Mar 2023 07:49:20 -0600 [thread overview]
Message-ID: <20230316134920.2913561-1-tromey@adacore.com> (raw)
A recent change to rs6000-aix-tdep.c broke the build. This patch
fixes it by declaring a few target descriptions in ppc-tdep.h and then
not including the various features .c files in rs6000-aix-tdep.c.
---
gdb/ppc-tdep.h | 6 ++++++
gdb/rs6000-aix-tdep.c | 5 -----
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/gdb/ppc-tdep.h b/gdb/ppc-tdep.h
index fe41baef149..db4e53205a6 100644
--- a/gdb/ppc-tdep.h
+++ b/gdb/ppc-tdep.h
@@ -450,4 +450,10 @@ struct ppc_inferior_data
extern ppc_inferior_data * get_ppc_per_inferior (inferior *inf);
+extern const struct target_desc *tdesc_powerpc_vsx64l;
+extern const struct target_desc *tdesc_powerpc_vsx64;
+extern const struct target_desc *tdesc_powerpc_vsx32;
+extern const struct target_desc *tdesc_powerpc_altivec64;
+extern const struct target_desc *tdesc_powerpc_altivec32;
+
#endif /* ppc-tdep.h */
diff --git a/gdb/rs6000-aix-tdep.c b/gdb/rs6000-aix-tdep.c
index c56e5a384e4..d4a7b22bc4f 100644
--- a/gdb/rs6000-aix-tdep.c
+++ b/gdb/rs6000-aix-tdep.c
@@ -40,11 +40,6 @@
#include "trad-frame.h"
#include "frame-unwind.h"
-#include "features/rs6000/powerpc-altivec32.c"
-#include "features/rs6000/powerpc-vsx32.c"
-#include "features/rs6000/powerpc-altivec64.c"
-#include "features/rs6000/powerpc-vsx64.c"
-
/* If the kernel has to deliver a signal, it pushes a sigcontext
structure on the stack and then calls the signal handler, passing
the address of the sigcontext in an argument register. Usually
--
2.39.1
next reply other threads:[~2023-03-16 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 13:49 Tom Tromey [this message]
2023-03-16 14:07 ` Luis Machado
2023-03-16 14:57 ` John Baldwin
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=20230316134920.2913561-1-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).