From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>,
Paul Brook <paul@codesourcery.com>,
Aurelien Jarno <aurelien@aurel32.net>,
patches@linaro.org
Subject: [Qemu-devel] [PATCH 0/6] target-arm: reduce usage of global env
Date: Wed, 25 May 2011 17:00:09 +0100 [thread overview]
Message-ID: <1306339215-1228-1-git-send-email-peter.maydell@linaro.org> (raw)
This patchset is largely aimed at rolling back the changes from an
earlier patchset of mine:
http://lists.gnu.org/archive/html/qemu-devel/2011-04/msg00244.html
which made various Neon helper routines use the correct FP status
flags by having them use the global env.
Since we've decided we're trying to get rid of the global CPUState
pointer (at least in C code), patches 1, 5, 6 here are basically
reverting patches 1,2,3 of that earlier patchset. In order not
to throw the baby out with the bathwater, patches 2, 3, 4 make
the helper routines which need to use the FP status take a pointer
to the fp status word. (In a few cases we can then merge them
with the equivalent VFP helpers.)
This obviously still leaves some global CPUState use in op_helper.c,
but it's a move in the right direction.
Peter Maydell (6):
Revert "target-arm: Use global env in iwmmxt_helper.c helpers"
target-arm: Add helper function to generate code to get fpstatus
pointer
target-arm: Make VFP binop helpers take pointer to fpstatus, not
CPUState
target-arm: Pass fp status pointer explicitly to neon fp helpers
Revert "target-arm: Use global env in neon_helper.c helpers"
Revert "Makefile.target: Allow target helpers to be in any *_helper.c
file"
Makefile.target | 2 +-
target-arm/helper.c | 10 +-
target-arm/helper.h | 293 +++++++++++++++---------------
target-arm/iwmmxt_helper.c | 80 +++++----
target-arm/neon_helper.c | 201 ++++++++++-----------
target-arm/translate.c | 431 ++++++++++++++++++++++++++------------------
6 files changed, 554 insertions(+), 463 deletions(-)
next reply other threads:[~2011-05-25 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 16:00 Peter Maydell [this message]
2011-05-25 16:00 ` [Qemu-devel] [PATCH 1/6] Revert "target-arm: Use global env in iwmmxt_helper.c helpers" Peter Maydell
2011-05-25 16:00 ` [Qemu-devel] [PATCH 2/6] target-arm: Add helper function to generate code to get fpstatus pointer Peter Maydell
2011-05-25 16:00 ` [Qemu-devel] [PATCH 3/6] target-arm: Make VFP binop helpers take pointer to fpstatus, not CPUState Peter Maydell
2011-05-25 16:00 ` [Qemu-devel] [PATCH 4/6] target-arm: Pass fp status pointer explicitly to neon fp helpers Peter Maydell
2011-05-25 16:00 ` [Qemu-devel] [PATCH 5/6] Revert "target-arm: Use global env in neon_helper.c helpers" Peter Maydell
2011-05-25 16:00 ` [Qemu-devel] [PATCH 6/6] Revert "Makefile.target: Allow target helpers to be in any *_helper.c file" Peter Maydell
2011-05-26 19:01 ` [Qemu-devel] [PATCH 0/6] target-arm: reduce usage of global env Blue Swirl
2011-05-26 19:34 ` Peter Maydell
2011-05-26 19:46 ` 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=1306339215-1228-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=patches@linaro.org \
--cc=paul@codesourcery.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).