From: "H.J. Lu" <hjl.tools@gmail.com>
To: GDB <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: [GDB 11 PATCH] gdb: clean up some things in features/Makefile
Date: Thu, 24 Feb 2022 09:06:34 -0800 [thread overview]
Message-ID: <Yhe7Gnr4DOm6Dl1S@gmail.com> (raw)
I am backporting this to GDB 11.
H.J.
---
- 32bit-segments.xml is not listed in the Makfile, but it's used. This
means that it wouldn't get re-generated if we were to change how C
files are generated from the XML. It looks like it was simply
forgotten, add it.
This fixes PR build/28921.
(cherry picked from commit 1056aa39196e0af454e6cdff193d7fd4bc638b9c)
---
gdb/features/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/features/Makefile b/gdb/features/Makefile
index 6fd7d463ccd..b8d722ef8c6 100644
--- a/gdb/features/Makefile
+++ b/gdb/features/Makefile
@@ -222,6 +222,7 @@ FEATURE_XMLFILES = aarch64-core.xml \
i386/32bit-mpx.xml \
i386/32bit-avx512.xml \
i386/32bit-pkeys.xml \
+ i386/32bit-segments.xml \
i386/64bit-avx512.xml \
i386/64bit-core.xml \
i386/64bit-mpx.xml \
--
2.35.1
reply other threads:[~2022-02-24 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Yhe7Gnr4DOm6Dl1S@gmail.com \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).