qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Matthew Fortune" <matthew.fortune@mips.com>,
	"Paul Burton" <paulburton@kernel.org>,
	"Stefan Markovic" <Stefan.Markovic@mips.com>,
	"Robert Suchanek" <Robert.Suchanek@mips.com>
Cc: James Hogan <jhogan@kernel.org>,
	Marcin Nowakowski <marcin.nowakowski@fungible.com>,
	zou xu <iwatchnima@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: target/mips: Deprecate nanoMIPS ISA?
Date: Mon, 2 Nov 2020 08:05:20 -0800	[thread overview]
Message-ID: <3fdc46f1-34a9-77ad-1183-249c17cfb3e9@linaro.org> (raw)
In-Reply-To: <38441531-1509-724f-4643-2ff2db253e3f@amsat.org>

On 11/2/20 2:00 AM, Philippe Mathieu-Daudé wrote:
> The toolchain page mention LLVM but simply links http://llvm.org/
> where I couldn't find any reference on nanoMIPS.
> 
> The only reference in the GCC mailing list, is the nanoMIPS
> announcement: https://gcc.gnu.org/pipermail/gcc/2018-May.txt
> 
> 
> It looks safe for QEMU to declare nanoMIPS deprecated (it has no
> maintainer), to give time to interested parties to finish upstreaming
> process and step in to maintain it.
> Thoughts?

I think that's reasonable.


r~


      parent reply	other threads:[~2020-11-02 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  1:12 [PATCH 1/1] accel/tcg/user-exec: support computing is_write for mips32 zou xu
2020-09-11 10:41 ` Peter Maydell
2020-09-11 16:55   ` Richard Henderson
2020-09-11 17:23     ` Philippe Mathieu-Daudé
2020-11-02 10:00       ` target/mips: Deprecate nanoMIPS ISA? Philippe Mathieu-Daudé
2020-11-02 11:27         ` Philippe Mathieu-Daudé
2020-11-02 16:05         ` Richard Henderson [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=3fdc46f1-34a9-77ad-1183-249c17cfb3e9@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=Robert.Suchanek@mips.com \
    --cc=Stefan.Markovic@mips.com \
    --cc=armbru@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=iwatchnima@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=marcin.nowakowski@fungible.com \
    --cc=matthew.fortune@mips.com \
    --cc=paulburton@kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).