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: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"Andreas Färber" <andreas.faerber@web.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] softfloat: Rename float*_is_nan() functions to float*_is_quiet_nan()
Date: Fri, 17 Dec 2010 21:30:11 -0500	[thread overview]
Message-ID: <20101218023011.GN25059@nightcrawler> (raw)
In-Reply-To: <AANLkTi=hx8ND8c4aFsxCavHXFT=QZK5v1O+4kZbjpDfH@mail.gmail.com>

On Fri, Dec 17, 2010 at 11:32:03PM +0000, Peter Maydell wrote:
> On 17 December 2010 17:54, Andreas Färber <andreas.faerber@web.de> wrote:
> > My patch does not touch the bits* types. I didn't notice any problem there.
> >
> > I replaced int32 by int32_t, int64 by int64_t etc. No sane code puts more
> > than 32 bits into an "int32" variable, and my guests on OSX/ppc64 host still
> > appeared to work. I don't have arm guests though so please check on your
> > side.
> 
> Hrm. That introduces potential semantic changes, so I'm a bit wary
> of it (and my test suite is not currently comprehensive enough to be
> sure of covering all of softfloat)... I'd be happier if we just renamed
> the int32 & friends to some other non-clashing name, if all we're
> trying to solve is a name clash issue.

I wouldn't be too worried:

typedef uint8_t flag;
typedef uint8_t uint8;
typedef int8_t int8;
typedef int uint16;
typedef int int16;
typedef unsigned int uint32;
typedef signed int int32;
typedef uint64_t uint64;
typedef int64_t int64;

So adding _t suffixes in appropriate places should be a no-op, except
for uint16/int16--and those types are never used.

-Nathan

  reply	other threads:[~2010-12-18  2:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 15:56 [Qemu-devel] [PATCH V2] softfloat: Rename float*_is_nan() functions to float*_is_quiet_nan() Peter Maydell
2010-12-17 16:19 ` Andreas Färber
2010-12-17 16:48   ` Peter Maydell
2010-12-17 17:54     ` Andreas Färber
2010-12-17 23:32       ` Peter Maydell
2010-12-18  2:30         ` Nathan Froyd [this message]
2010-12-18 10:39           ` Peter Maydell
2010-12-18 11:49             ` Andreas Färber
2010-12-18 12:15               ` Peter Maydell
2010-12-18 12:31                 ` Andreas Färber
2010-12-18 16:41                   ` Andreas Färber
2010-12-18 17:55               ` malc
2010-12-18 13:07             ` Nathan Froyd
2011-01-01 23:46 ` Peter Maydell
2011-01-02  0:35   ` Andreas Färber
2011-01-02 10:31   ` Aurelien Jarno
2011-01-02 11:12     ` Peter Maydell
2011-01-02 11:56       ` Aurelien Jarno

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=20101218023011.GN25059@nightcrawler \
    --to=froydnj@codesourcery.com \
    --cc=andreas.faerber@web.de \
    --cc=edgar.iglesias@gmail.com \
    --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).