From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Riku Voipio <riku.voipio@iki.fi>, Laurent Vivier <Laurent@vivier.eu>
Subject: Re: [Qemu-devel] linux-user: drop support for "unknown" host CPUs (ie hppa and m68k) ?
Date: Mon, 13 Jun 2016 15:06:48 -0700 [thread overview]
Message-ID: <86b7f579-1369-92b0-a060-c4e7449cb485@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8Bkh4-jjDKNjOxgNQhm+-tGSLE4Opz2wEptkMuGQKaqQ@mail.gmail.com>
On 06/13/2016 02:26 AM, Peter Maydell wrote:
> Currently our configure script allows linux-user targets to be built
> for "unknown" host CPU architectures (which must be using the TCI
> interpreter). However, code like user-exec.c has host-architecture
> #ifdef ladders which in practice mean you can't build linux-user for
> an arbitrary host architecture. The only two host architectures which
> have code in user-exec.c but aren't recognised by configure are
> HPPA and m68k.
>
> I'd like to move to an "every supported host architecture has a
> linux-user/host/$(ARCH)/hostdep.h header" model (this fixes a problem
> in the code currently in master where make doesn't notice it needs to
> rebuild if a host arch moves from "using generic/" to "using $(ARCH)").
> Host architectures which we sort-of-but-don't support are an annoying
> corner case I'd like to be able to drop entirely, by either:
> (1) just dropping the support outright
I'm ok with this.
r~
prev parent reply other threads:[~2016-06-13 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 9:26 [Qemu-devel] linux-user: drop support for "unknown" host CPUs (ie hppa and m68k) ? Peter Maydell
2016-06-13 9:40 ` Laurent Vivier
2016-06-13 22:06 ` 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=86b7f579-1369-92b0-a060-c4e7449cb485@twiddle.net \
--to=rth@twiddle.net \
--cc=Laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).