From: Nathan Froyd <froydnj@codesourcery.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 1/7] target-arm: Make Neon helper routines use correct FP status
Date: Sun, 13 Mar 2011 22:35:59 -0700 [thread overview]
Message-ID: <20110314053558.GA30619@codesourcery.com> (raw)
In-Reply-To: <AANLkTikicYzL7wLHQWP2=h7w5pgvuWhJpK38jChFz6Ff@mail.gmail.com>
On Fri, Mar 11, 2011 at 10:31:31PM +0000, Peter Maydell wrote:
> On 11 March 2011 18:30, Nathan Froyd <froydnj@codesourcery.com> wrote:
> > Is there a reason that you don't simply use the global env rather than
> > passing in an extra parameter everywhere?
>
> Just following the pattern that generally seems to be used by
> most helper functions, ie if you want the CPU env pass it in
> as a parameter. As far as I know, you can't use the global
> env unless you're in op_helper.c because that's the only
> source file compiled with the right flags.
Oh, right. I am ambivalent as to whether passing env to such functions
is the right thing to do or not.
> > I wonder if it'd be worthwhile just to merge these functions into
> > op_helper.c, since we have a proper FP status for NEON bits now.
>
> Why move these and not (for instance) the VFP helpers
> in helper.c which use the CPU env for more or less the
> same reasons?
No reason, other than that I wasn't thinking about the VFP helpers. :)
-Nathan
next prev parent reply other threads:[~2011-03-14 5:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 18:12 [Qemu-devel] [PATCH 0/7] ARM: minor Neon fixes (mostly NaN related) Peter Maydell
2011-03-11 18:12 ` [Qemu-devel] [PATCH 1/7] target-arm: Make Neon helper routines use correct FP status Peter Maydell
2011-03-11 18:30 ` Nathan Froyd
2011-03-11 22:31 ` Peter Maydell
2011-03-14 5:35 ` Nathan Froyd [this message]
2011-03-28 14:15 ` Peter Maydell
2011-03-30 18:38 ` Nathan Froyd
2011-03-11 18:12 ` [Qemu-devel] [PATCH 2/7] target-arm/neon_helper.c: Use make_float32/float32_val macros Peter Maydell
2011-03-11 18:29 ` Nathan Froyd
2011-03-11 18:12 ` [Qemu-devel] [PATCH 3/7] target-arm: Return right result for Neon comparison with NaNs Peter Maydell
2011-03-11 18:12 ` [Qemu-devel] [PATCH 4/7] target-arm: Fix VCLE.F32 #0, VCLT.F32 #0 NaN handling Peter Maydell
2011-03-11 18:12 ` [Qemu-devel] [PATCH 5/7] target-arm: Correct ABD's handling of negative zeroes Peter Maydell
2011-03-11 18:12 ` [Qemu-devel] [PATCH 6/7] softfloat: Add float*_min() and float*_max() functions Peter Maydell
2011-03-11 18:28 ` Nathan Froyd
2011-03-11 23:31 ` Peter Maydell
2011-03-11 18:12 ` [Qemu-devel] [PATCH 7/7] target-arm: Use new softfloat min/max functions for VMAX, VMIN 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=20110314053558.GA30619@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=patches@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.