qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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] target-arm/helper.c: For float-int conversion helpers pass ints as ints
Date: Mon, 21 Mar 2011 07:09:21 -0700	[thread overview]
Message-ID: <20110321140921.GL30619@codesourcery.com> (raw)
In-Reply-To: <AANLkTin__xQYUSwrRTcumXkeF+aPwy1kA_Cagy=bZaF3@mail.gmail.com>

On Mon, Mar 21, 2011 at 02:04:31PM +0000, Peter Maydell wrote:
> On 21 March 2011 13:48, Nathan Froyd <froydnj@codesourcery.com> wrote:
> > I like the direction this patch goes; you aren't by any chance going to
> > convert the passing/returning of float* to their appropriate int* types
> > too, are you?
> 
> Nope -- I think that where we're passing or returning an actual
> IEEE single/double to a helper function "float*" is a better type
> than uint32_t: it gives information about what the helper's argument
> semantically is, and it means we don't have every helper that takes
> or returns a float have to include ugly calls to the boxing/unboxing
> macros.

I'm just concerned about what would happen if we turned on softfloat's
"float types are structure types" bit; I'm pretty sure everything would
break horribly on targets that don't pass small structures in
registers.  Admittedly, several targets would be broken by doing so, so
it's not particularly urgent.

-Nathan

  reply	other threads:[~2011-03-21 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 17:23 [Qemu-devel] [PATCH] target-arm/helper.c: For float-int conversion helpers pass ints as ints Peter Maydell
2011-03-21 13:48 ` Nathan Froyd
2011-03-21 14:04   ` Peter Maydell
2011-03-21 14:09     ` Nathan Froyd [this message]
2011-03-21 14:27       ` 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=20110321140921.GL30619@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 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).