From: Thomas Huth <thuth@redhat.com>
To: Milica Lazarevic <Milica.Lazarevic@Syrmia.com>
Cc: "cfontana@suse.de" <cfontana@suse.de>,
"berrange@redhat.com" <berrange@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
Djordje Todorovic <Djordje.Todorovic@syrmia.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Vince Del Vecchio <Vince.DelVecchio@mediatek.com>
Subject: Re: What to do with the nanomips disassembler (was: [PATCH] disas: Remove libvixl disassembler)
Date: Fri, 8 Jul 2022 21:53:58 +0200 [thread overview]
Message-ID: <cf15780a-b02e-dc88-954c-6f90d6ba5107@redhat.com> (raw)
In-Reply-To: <VE1PR03MB60454933EBCDB900C8A9AAD4F8BE9@VE1PR03MB6045.eurprd03.prod.outlook.com>
On 04/07/2022 14.22, Milica Lazarevic wrote:
>
> On 09/06/2022 18.31, Vince Del Vecchio wrote:
...
> Regardless, I think we can look at converting the existing disassembler from
> C++ to C. That would address the current concern, right?
>
> > Right - if it's not too much of a hassle that would be great!
>
> Hi everyone, I am interested in taking on this task.
Since nobody else replied, I assume nobody started working on this task yet,
so I'd say: Please go ahead and convert that file to plain C!
Thanks,
Thomas
next prev parent reply other threads:[~2022-07-08 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 12:22 What to do with the nanomips disassembler (was: [PATCH] disas: Remove libvixl disassembler) Milica Lazarevic
2022-07-08 19:53 ` Thomas Huth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-04 12:12 Milica Lazarevic
2022-06-03 16:42 [PATCH] disas: Remove libvixl disassembler Thomas Huth
2022-06-03 17:26 ` Claudio Fontana
2022-06-03 17:35 ` Thomas Huth
2022-06-08 15:51 ` Paolo Bonzini
2022-06-09 8:47 ` Thomas Huth
2022-06-09 8:57 ` Daniel P. Berrangé
2022-06-09 11:27 ` Claudio Fontana
2022-06-09 14:15 ` Claudio Fontana
2022-06-09 14:34 ` What to do with the nanomips disassembler (was: [PATCH] disas: Remove libvixl disassembler) Thomas Huth
2022-06-09 16:31 ` Vince Del Vecchio via
2022-06-09 17:36 ` Thomas Huth
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=cf15780a-b02e-dc88-954c-6f90d6ba5107@redhat.com \
--to=thuth@redhat.com \
--cc=Djordje.Todorovic@syrmia.com \
--cc=Milica.Lazarevic@Syrmia.com \
--cc=Vince.DelVecchio@mediatek.com \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 NNTP newsgroup(s).