[lkml]   [2013]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH jiffies] Avoid undefined behavior from signed overflow
Quoting "Paul E. McKenney" <>:

> On Mon, Jul 29, 2013 at 03:30:35PM +1000, wrote:
>> Quoting "Paul E. McKenney" <>:
>> >
>> >Note that the C standard considers the cast from signed to
>> >unsigned to be implementation-defined, see
>> Don't worry, the case from signed to unsigned is actually well-defined -
>> the relevant part is (in C99):
>> >Otherwise, if the new type is unsigned, the value is converted by
>> >repeatedly adding or subtracting one more than the maximum value that
>> >can be represented in the new type until the value is in the range of
>> >the new type.
> Yep, but we are going in the other direction, from unsigned to signed.

Ahh, there's an error in the commit message (it says signed to unsigned).

- Kevin

This message was sent using IMP, the Internet Messaging Program.

 \ /
  Last update: 2013-07-29 17:01    [W:0.060 / U:17.420 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site