public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/nds32: update features/nds32.c
Date: Sun, 14 Aug 2022 13:54:43 +0000 (GMT)	[thread overview]
Message-ID: <20220814135443.D03533858D1E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ceb3ca2f7d700f79bd3d7f7d3c9aee204e344127

commit ceb3ca2f7d700f79bd3d7f7d3c9aee204e344127
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Thu Aug 11 15:57:26 2022 +0100

    gdb/nds32: update features/nds32.c
    
    After this commit:
    
      commit 7b7c365c5c663ffdfb2b3f696db35c23cdccd921
      Date:   Wed Sep 15 10:10:46 2021 +0200
    
          [bfd] Ensure unique printable names for bfd archs
    
    The printable name field of the default nds32 bfd_arch_info changed
    from 'n1h' to 'n1'.  As a consequence the generated feature file
    within GDB should have been recreated.  Recreate it now.

Diff:
---
 gdb/features/nds32.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/features/nds32.c b/gdb/features/nds32.c
index ed535b5ab9f..4e520163931 100644
--- a/gdb/features/nds32.c
+++ b/gdb/features/nds32.c
@@ -10,7 +10,7 @@ static void
 initialize_tdesc_nds32 (void)
 {
   target_desc_up result = allocate_target_description ();
-  set_tdesc_architecture (result.get (), bfd_scan_arch ("n1h"));
+  set_tdesc_architecture (result.get (), bfd_scan_arch ("n1"));
 
   struct tdesc_feature *feature;


                 reply	other threads:[~2022-08-14 13: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:
  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=20220814135443.D03533858D1E@sourceware.org \
    --to=aburgess@sourceware.org \
    --cc=gdb-cvs@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).