From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
toolchain-devel@blackfin.uclinux.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] new Blackfin QEMU port
Date: Tue, 1 Feb 2011 11:53:14 +0000 [thread overview]
Message-ID: <AANLkTinpgL1xUzk7_fqMwyV2fB0=5vd0c9gEUC42ncsm@mail.gmail.com> (raw)
In-Reply-To: <6ADF7310-2588-4FD5-BA21-2A31456B3E2B@suse.de>
On 1 February 2011 11:46, Alexander Graf <agraf@suse.de> wrote:
> Ouch. Yes. General rule: never access env from translate.c :).
With the arm target I was tempted to restructure translate.c so
that we copied the handful of "safe" bits of env that we used
into the disas context struct right at the start, and then didn't
pass env into the main translation functions at all. That would
make it much harder to accidentally use bits of env that we
should not, but in the end I decided against it because it would
make my qemu-meego merging job that much harder...
-- PMM
next prev parent reply other threads:[~2011-02-01 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 10:23 [Qemu-devel] [PATCH 0/4] new Blackfin QEMU port Mike Frysinger
2011-01-24 10:26 ` [Qemu-devel] [PATCH 3/4] Blackfin: add linux-user support Mike Frysinger
2011-01-24 10:29 ` [Qemu-devel] [PATCH 2/4] Blackfin: initial port Mike Frysinger
2011-01-31 14:00 ` [Qemu-devel] [PATCH 0/4] new Blackfin QEMU port Edgar E. Iglesias
2011-02-01 4:19 ` Mike Frysinger
2011-02-01 9:38 ` Alexander Graf
2011-02-01 10:31 ` Peter Maydell
2011-02-01 11:46 ` Alexander Graf
2011-02-01 11:53 ` Peter Maydell [this message]
2011-02-01 17:20 ` Mike Frysinger
2011-02-01 17:30 ` Peter Maydell
2011-02-01 18:16 ` Mike Frysinger
2011-02-01 18:45 ` Peter Maydell
2011-02-02 0:19 ` Mike Frysinger
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='AANLkTinpgL1xUzk7_fqMwyV2fB0=5vd0c9gEUC42ncsm@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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).