From: Nicolas Bareil <nico@chdir.org>
To: David Stevens <dlstevens@us.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re: [BUG] before() integer overflow
Date: Tue, 05 Aug 2008 20:24:27 +0200 [thread overview]
Message-ID: <87pronqq04.fsf@chdir.org> (raw)
In-Reply-To: <OFD6FD9FE8.66BA8559-ON8825749C.00619B98-8825749C.00621A40@us.ibm.com> (David Stevens's message of "Tue, 5 Aug 2008 10:51:32 -0700")
David Stevens <dlstevens@us.ibm.com> writes:
> In the sequence space, 0xffffffff is before 0 (by 1), so
> before() should return true. In your example, you don't have enough
> f's for it to be -1 as a signed number, so I'm assuming you mean
> 8 of them there. If you mean 6 f's, then the result is not -1, but the
> positive number 0xffffff, which returns false.
Yes I meant 8 f (I should change my too small fonts ;) )
Thanks to Ben for his explanation, I thought the PAWS was handled in a
specific way. Sorry!
--
Nicolas Bareil http://chdir.org/~nico/
OpenPGP=0xAE4F7057 Fingerprint=34DB22091049FB2F33E6B71580F314DAAE4F7057
prev parent reply other threads:[~2008-08-05 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 17:19 [BUG] before() integer overflow Nicolas Bareil
2008-08-05 17:40 ` Ben Hutchings
2008-08-05 17:51 ` David Stevens
2008-08-05 18:24 ` Nicolas Bareil [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=87pronqq04.fsf@chdir.org \
--to=nico@chdir.org \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.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).