From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] bfd: Add support for nanoMIPS architecture
Date: Sun, 1 May 2022 23:56:28 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2205012353340.9383@angie.orcam.me.uk> (raw)
In-Reply-To: <20220429155813.388328-2-aleksandar.rikalo@syrmia.com>
Hi Aleksandar,
> create mode 100644 bfd/cpu-nanomips.c
> create mode 100644 bfd/elfnn-nanomips.c
> create mode 100644 bfd/elfxx-nanomips.c
> create mode 100644 bfd/elfxx-nanomips.h
> create mode 100644 include/elf/mips-common.h
> create mode 100644 include/elf/nanomips.h
> create mode 100644 include/opcode/nanomips.h
> create mode 100644 opcodes/nanomips-dis.c
> create mode 100644 opcodes/nanomips-formats.h
> create mode 100644 opcodes/nanomips-opc.c
BFD/opcodes changes need to be sent to <binutils@sourceware.org>. Please
consult the MAINTAINERS file at the top level for what mailing list to use
for individual subdirectories.
Maciej
next prev parent reply other threads:[~2022-05-01 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220429155813.388328-1-aleksandar.rikalo@syrmia.com>
2022-04-29 15:58 ` Aleksandar Rikalo
2022-05-01 22:56 ` Maciej W. Rozycki [this message]
2022-04-29 15:58 ` [PATCH 2/3] sim: Add nanoMIPS port Aleksandar Rikalo
2022-05-04 12:45 ` Mike Frysinger
2022-11-21 11:06 ` [PATCH v3 1/2] " Aleksandar Rikalo
2022-11-21 11:06 ` [PATCH v3 2/2] gdb: " Aleksandar Rikalo
2022-12-12 9:42 ` Mike Frysinger
2022-12-12 9:45 ` Mike Frysinger
2022-11-25 12:11 ` [PATCH v3 1/2] sim: " Mike Frysinger
2022-11-25 15:36 ` Aleksandar Rikalo
2022-12-12 11:11 ` Mike Frysinger
2022-04-29 15:58 ` [PATCH 3/3] gdb: " Aleksandar Rikalo
2022-04-29 16:15 ` Eli Zaretskii
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=alpine.DEB.2.21.2205012353340.9383@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--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).