qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Olivier DANET <odanet@caramail.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re : Re: [PATCH] sparc32 : Signed integer division overflow
Date: Tue, 18 Mar 2014 19:44:27 -0700	[thread overview]
Message-ID: <5329048B.5000909@twiddle.net> (raw)
In-Reply-To: <20140318234357.21950@gmx.com>

On 03/18/2014 04:43 PM, Olivier DANET wrote:
>>> - x0 = x0 < 0 ? 0x80000000 : 0x7fffffff;
>>> > > + } else if (x1 == -1 && x0 == 0x8000000000000000) {
>>> > > + x0 = 0x7fffffff;
>>> > > overflow = 1;
>> > 
>> > Thanks for the patch! I think based upon Peter's recent series that the 
>> > sign constant would need a ULL suffix in order to function correctly on 
>> > 32-bit platforms.
>> > 
>> > My personal preference would be for (1ULL << 63) unless Peter (CC added) 
>> > can think of a reason to leave the hex constant in its current form?
>> > 
>> > That said, I've tested the patch on a Debian etch Linux image and it 
>> > works for me.
>> > 
> The constant lacks an "ULL" indeed, sorry.
> 
> There are both (1ULL << 63) and 0x8000000000000000[ULL] constants in QEMU code, 
> and not a single 9223372036854775808ULL...
> 
> At least, with (1ULL << 63), we are not tempted to count the zeros.

Not to bike-shed this too much, but INT32_MIN and INT64_MIN would be better and
more descriptive for these.  Honestly, we're supposed to be dealing with signed
numbers here, not the unsigned number you're creating above.


r~

      reply	other threads:[~2014-03-19  2:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 23:43 [Qemu-devel] Re : Re: [PATCH] sparc32 : Signed integer division overflow Olivier DANET
2014-03-19  2:44 ` Richard Henderson [this message]

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=5329048B.5000909@twiddle.net \
    --to=rth@twiddle.net \
    --cc=blauwirbel@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=odanet@caramail.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).