public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb: Add nanoMIPS port
Date: Tue, 31 May 2022 14:56:32 +0300	[thread overview]
Message-ID: <83pmjtj4pb.fsf@gnu.org> (raw)
In-Reply-To: <20220531113506.2494820-2-aleksandar.rikalo@syrmia.com> (message from Aleksandar Rikalo on Tue, 31 May 2022 13:35:06 +0200)

> From: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>
> Date: Tue, 31 May 2022 13:35:06 +0200
> 
>  config.sub                                    |    1 +
>  configure                                     |    3 +
>  configure.ac                                  |    3 +
>  gdb/Makefile.in                               |    2 +
>  gdb/NEWS                                      |    1 +
>  gdb/configure.host                            |    1 +
>  gdb/configure.tgt                             |   11 +
>  gdb/features/Makefile                         |    4 +
>  gdb/features/nanomips-cp0.xml                 |   13 +
>  gdb/features/nanomips-cpu.xml                 |   44 +
>  gdb/features/nanomips-dsp.xml                 |   20 +
>  gdb/features/nanomips-fpu.xml                 |   45 +
>  gdb/features/nanomips.c                       |   54 +
>  gdb/features/nanomips.xml                     |   12 +
>  gdb/features/nanomips64-cp0.xml               |   13 +
>  gdb/features/nanomips64-cpu.xml               |   44 +
>  gdb/features/nanomips64-dsp.xml               |   20 +
>  gdb/nanomips-tdep.c                           | 3410 +++++++++++++++++
>  gdb/nanomips-tdep.h                           |  144 +
>  gdb/testsuite/gdb.asm/asm-source.exp          |    9 +-
>  gdb/testsuite/gdb.asm/nanomips.inc            |   49 +
>  .../gdb.base/catch-gdb-caused-signals.c       |    3 +
>  gdb/testsuite/gdb.base/float.exp              |    2 +-
>  gdb/testsuite/gdb.trace/trace-common.h        |    2 +-
>  gdb/testsuite/lib/gdb.exp                     |    1 +
>  25 files changed, 3908 insertions(+), 3 deletions(-)
>  create mode 100644 gdb/features/nanomips-cp0.xml
>  create mode 100644 gdb/features/nanomips-cpu.xml
>  create mode 100644 gdb/features/nanomips-dsp.xml
>  create mode 100644 gdb/features/nanomips-fpu.xml
>  create mode 100644 gdb/features/nanomips.c
>  create mode 100644 gdb/features/nanomips.xml
>  create mode 100644 gdb/features/nanomips64-cp0.xml
>  create mode 100644 gdb/features/nanomips64-cpu.xml
>  create mode 100644 gdb/features/nanomips64-dsp.xml
>  create mode 100644 gdb/nanomips-tdep.c
>  create mode 100644 gdb/nanomips-tdep.h
>  create mode 100644 gdb/testsuite/gdb.asm/nanomips.inc

Thanks, the addition to NEWS is okay.

      reply	other threads:[~2022-05-31 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 11:35 [PATCH v2 1/2] sim: " Aleksandar Rikalo
2022-05-31 11:35 ` [PATCH v2 2/2] gdb: " Aleksandar Rikalo
2022-05-31 11:56   ` Eli Zaretskii [this message]

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=83pmjtj4pb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aleksandar.rikalo@syrmia.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).