From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Michael Clark" <mjc@sifive.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alistair Francis" <alistair23@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] configure: Add RISC-V host support
Date: Tue, 31 Jul 2018 10:30:43 +0100 [thread overview]
Message-ID: <20180731093043.GC29167@redhat.com> (raw)
In-Reply-To: <CAFEAcA_nr=hS4Qe=n-=HU389S5cvZArt97QJ83jLQ-x2xRKFWQ@mail.gmail.com>
On Mon, Jul 30, 2018 at 07:37:55PM +0100, Peter Maydell wrote:
> On 30 July 2018 at 19:20, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> > Before this patch:
> >
> > $ ./configure
> >
> > ERROR: Unsupported CPU = riscv64, try --enable-tcg-interpreter
> >
> > $ ./configure --enable-tcg-interpreter
> > Unsupported CPU = riscv64, will use TCG with TCI (experimental)
> >
> > [...]
> >
> > WARNING: SUPPORT FOR THIS HOST CPU WILL GO AWAY IN FUTURE RELEASES!
>
>
> > It is unlikely the RISC-V port goes away in the next future releases :)
>
> ...but it is not supported as a *host* CPU.
>
> We should fix this somewhat nonsensical error message by
> completing the deprecate-and-drop cycle for this bit of
> configure, ie by outright rejecting attempts to build on
> host CPU types we don't recognize and support, the same
> way we do with unrecognized host OS types.
Do you mean to imply that we should drop the TCG intepreter too, or do
you consider that something that makes it a supported host CPU ? TCG
intepretor essentially makes any host supportable, if we keep it.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-07-31 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 23:49 [Qemu-devel] [PATCH v1 1/1] configure: Add RISC-V host support Alistair Francis
2018-07-28 4:14 ` Michael Clark
2018-07-28 16:36 ` Richard Henderson
2018-07-29 11:28 ` Peter Maydell
2018-07-30 17:24 ` Alistair Francis
2018-07-30 18:33 ` Peter Maydell
2018-07-30 18:20 ` Philippe Mathieu-Daudé
2018-07-30 18:37 ` Peter Maydell
2018-07-31 9:30 ` Daniel P. Berrangé [this message]
2018-07-31 9:39 ` Peter Maydell
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=20180731093043.GC29167@redhat.com \
--to=berrange@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=f4bug@amsat.org \
--cc=mjc@sifive.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.