From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Laurent@vivier.eu
Subject: Re: [PATCH 4/5] linux-user: Move sparc/host-signal.h to sparc64/host-signal.h
Date: Tue, 8 Feb 2022 22:19:22 +1100 [thread overview]
Message-ID: <87706007-982b-eaaa-eca6-00dfd33a15d2@linaro.org> (raw)
In-Reply-To: <CAFEAcA-XH1yc-NbFQAgXo7BAtiVBgCACQ70EWf6CjndXaZVqBw@mail.gmail.com>
On 2/8/22 22:01, Peter Maydell wrote:
> On Tue, 8 Feb 2022 at 08:17, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> We do not support sparc32 as a host, so there's no point in
>> sparc64 redirecting to sparc.
>
> Where do we enforce that ? I couldn't see anything in
> configure or meson.build that forbids linux-user with
> a 32-bit sparc host, but I probably missed it.
The common-user/host/sparc directory is missing; meson will error out.
r~
next prev parent reply other threads:[~2022-02-08 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 7:12 [PATCH 0/5] linux-user: Fixes for sparc64 host Richard Henderson
2022-02-08 7:12 ` [PATCH 1/5] common-user/host/sparc64: Fix safe_syscall_base Richard Henderson
2022-02-08 7:12 ` [PATCH 2/5] linux-user: Introduce host_signal_mask Richard Henderson
2022-02-08 10:39 ` Philippe Mathieu-Daudé via
2022-02-08 10:59 ` Peter Maydell
2022-02-08 11:17 ` Richard Henderson
2022-02-08 11:32 ` Peter Maydell
2022-02-08 7:12 ` [PATCH 3/5] linux-user: Introduce host_sigcontext Richard Henderson
2022-02-08 10:40 ` Philippe Mathieu-Daudé via
2022-02-08 11:06 ` Peter Maydell
2022-02-08 7:12 ` [PATCH 4/5] linux-user: Move sparc/host-signal.h to sparc64/host-signal.h Richard Henderson
2022-02-08 10:40 ` Philippe Mathieu-Daudé via
2022-02-08 11:01 ` Peter Maydell
2022-02-08 11:19 ` Richard Henderson [this message]
2022-02-08 7:12 ` [PATCH 5/5] linux-user/include/host/sparc64: Fix host_sigcontext Richard Henderson
2022-02-08 11:14 ` 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=87706007-982b-eaaa-eca6-00dfd33a15d2@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).