public inbox for
help / color / mirror / Atom feed
From: Tiezhu Yang <>
Subject: [binutils-gdb] gdb: NEWS: Move LoongArch gdbserver to the correct section
Date: Fri, 17 Jun 2022 12:54:01 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=02e85f7a8304ed192382391dc83c0211345b40d1

commit 02e85f7a8304ed192382391dc83c0211345b40d1
Author: Tiezhu Yang <>
Date:   Fri Jun 17 16:51:05 2022 +0800

    gdb: NEWS: Move LoongArch gdbserver to the correct section
    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.
    Signed-off-by: Tiezhu Yang <>

 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:
@@ -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-*

                 reply	other threads:[~2022-06-17 12:54 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).