From: Mike Frysinger <vapier@gentoo.org>
To: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>
Cc: gdb-patches@sourceware.org, arikalo@gmail.com
Subject: Re: [PATCH v3 2/2] gdb: Add nanoMIPS port
Date: Mon, 12 Dec 2022 18:45:35 +0900 [thread overview]
Message-ID: <Y5b4P51YaYHiOr4U@vapier> (raw)
In-Reply-To: <20221121110603.124056-2-aleksandar.rikalo@syrmia.com>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
On 21 Nov 2022 12:06, Aleksandar Rikalo wrote:
> --- a/gdb/configure.tgt
> +++ b/gdb/configure.tgt
> @@ -448,6 +448,16 @@ msp430-*-elf*)
> gdb_target_obs="msp430-tdep.o"
> ;;
>
> +mt-*-*)
> + # Target: Morpho Technologies ms1 processor
> + gdb_target_obs="mt-tdep.o"
> + ;;
this patch is about nanomips, not this thing
> --- /dev/null
> +++ b/gdb/nanomips-tdep.c
this file seems to duplicate a lot of existing mips-tdep.c logic.
can't they be merged/kept in sync better ?
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-12 9:45 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 ` [PATCH 1/3] bfd: Add support for nanoMIPS architecture Aleksandar Rikalo
2022-05-01 22:56 ` Maciej W. Rozycki
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 [this message]
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=Y5b4P51YaYHiOr4U@vapier \
--to=vapier@gentoo.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.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).