From: Peter Maydell <peter.maydell@linaro.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 01/11] Move user emulator stuff from cpu-exec.c to user-exec.c
Date: Tue, 17 May 2011 15:52:04 +0100 [thread overview]
Message-ID: <BANLkTikWkPu8NBEUAAjtyw33G8RyJuwKKw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTiksFDsZRin=drOg2hk5uCtsBpNKwg@mail.gmail.com>
On 14 May 2011 20:36, Blue Swirl <blauwirbel@gmail.com> wrote:
> +#if defined(__i386__)
> +#elif defined(__x86_64__)
> +#elif defined(_ARCH_PPC)
> +#elif defined(__alpha__)
> +#elif defined(__sparc__)
> +#elif defined(__arm__)
> +#elif defined(__mc68000)
> +#elif defined(__ia64)
> +#elif defined(__s390__)
> +#elif defined(__mips__)
> +#elif defined(__hppa__)
...if we're moving this code about anyway would it be possible
to split the per-host-arch specific code out into separate files?
I find these source files with enormous ifdef ladders pretty hard
to read.
-- PMM
next prev parent reply other threads:[~2011-05-17 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 19:36 [Qemu-devel] [PATCH 01/11] Move user emulator stuff from cpu-exec.c to user-exec.c Blue Swirl
2011-05-17 14:40 ` Richard Henderson
2011-05-17 14:52 ` Peter Maydell [this message]
2011-05-17 19:46 ` Blue Swirl
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=BANLkTikWkPu8NBEUAAjtyw33G8RyJuwKKw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=blauwirbel@gmail.com \
--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).