From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Aleksandar Rikalo <Aleksandar.Rikalo@syrmia.com>,
Vince Del Vecchio <Vince.DelVecchio@mediatek.com>,
Richard Henderson <richard.henderson@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "paulburton@kernel.org" <paulburton@kernel.org>,
Stefan Weil <sw@weilnetz.de>,
"chenhuacai@kernel.org" <chenhuacai@kernel.org>,
Petar Jovanovic <petar.jovanovic@syrmia.com>,
"aurelien@aurel32.net" <aurelien@aurel32.net>,
Filip Vidojevic <Filip.Vidojevic@Syrmia.com>
Subject: Re: [PATCH v2] Revert "target/mips: Deprecate nanoMIPS ISA"
Date: Tue, 20 Apr 2021 18:47:36 +0200 [thread overview]
Message-ID: <c8560e72-0775-031f-3304-1eb762224265@amsat.org> (raw)
In-Reply-To: <VI1PR0302MB3486B078E5E08DF7EC15792C9C489@VI1PR0302MB3486.eurprd03.prod.outlook.com>
On 4/20/21 6:06 PM, Aleksandar Rikalo wrote:
> Hi Philippe,
>
>> The plan is to drop the nanoMIPS disassembler because it is broken
>> since more than 2 years and nobody ever cared to fix it after Stefan's
>> attempt in Nov 2018:
>> https://www.mail-archive.com/qemu-devel@nongnu.org/msg576504.html
>> So it is certainly unused. Unused unmaintained code has a cost and
>> negative impact to the generic project development.
>
> How do you conclude it is broken ? It seems to work well.
> Aleksandar Markovic did few fixes during 2019.
One community user tried it, reported a bug which got never
fixed. This means the code is not used by the mainstream community,
but is a burden for maintenance.
>
> NanoMIPS needs disassembler, like other architectures...
I totally agreed, but we need a working disassembler; this is why
I started looking for other alternatives (binutils libopcodes or
capstone) and realized nanoMIPS toolchain was never upstreamed,
so started the deprecation process.
next prev parent reply other threads:[~2021-04-20 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210408085810.10567-1-Filip.Vidojevic@Syrmia.com>
2021-04-08 17:01 ` [PATCH v2] Revert "target/mips: Deprecate nanoMIPS ISA" Aleksandar Rikalo
2021-04-08 18:16 ` Richard Henderson
2021-04-09 1:10 ` Vince Del Vecchio
2021-04-09 14:44 ` Richard Henderson
2021-04-19 18:11 ` Philippe Mathieu-Daudé
2021-04-20 16:06 ` Aleksandar Rikalo
2021-04-20 16:47 ` Philippe Mathieu-Daudé [this message]
2021-04-20 23:24 ` Petar Jovanovic
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=c8560e72-0775-031f-3304-1eb762224265@amsat.org \
--to=f4bug@amsat.org \
--cc=Aleksandar.Rikalo@syrmia.com \
--cc=Filip.Vidojevic@Syrmia.com \
--cc=Vince.DelVecchio@mediatek.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@kernel.org \
--cc=paulburton@kernel.org \
--cc=petar.jovanovic@syrmia.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).