From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: gdb-patches@sourceware.org
Subject: [OB COMMITTED PATCH] gdb: NEWS: Move LoongArch gdbserver to the correct section
Date: Fri, 17 Jun 2022 20:56:18 +0800 [thread overview]
Message-ID: <20220617125618.4779-1-yangtiezhu@loongson.cn> (raw)
commit e5ab6af52d38 ("gdbserver: Add LoongArch/Linux support")
was merged into the master since GDB 12, so we should put the
news in the "Changes since GDB 12" section.
Thanks Tom Tromey for your correction [1], sorry for that.
[1] https://sourceware.org/pipermail/gdb-patches/2022-June/190122.html
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
---
gdb/NEWS | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index ac9a1aacd34..c570681a977 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -43,6 +43,10 @@ maintenance info line-table
entry corresponds to an address where a breakpoint should be placed
to be at the first instruction past a function's prologue.
+* New targets
+
+GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
+
* Python API
** GDB will now reformat the doc string for gdb.Command and
@@ -97,6 +101,10 @@ maintenance info line-table
to wrap the result of a call to a Disassembler. It has
read-only attributes 'length' and 'string'.
+* New features in the GDB remote stub, GDBserver
+
+ ** GDBserver is now supported on LoongArch GNU/Linux.
+
*** Changes in GDB 12
* DBX mode is deprecated, and will be removed in GDB 13
@@ -728,8 +736,6 @@ QMemTags
** GDBserver is now supported on RISC-V GNU/Linux.
- ** GDBserver is now supported on LoongArch GNU/Linux.
-
** GDBserver no longer supports these host triplets:
i[34567]86-*-lynxos*
@@ -821,7 +827,6 @@ alias [-a] [--] ALIAS = COMMAND [DEFAULT-ARGS...]
* New targets
GNU/Linux/RISC-V (gdbserver) riscv*-*-linux*
-GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
BPF bpf-unknown-none
Z80 z80-unknown-*
--
2.27.0
reply other threads:[~2022-06-17 12:56 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=20220617125618.4779-1-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--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).