On Thu Mar 3 06:18:48 UTC 2016 Bruce Evans wrote:
> On Thu, 3 Mar 2016, Justin Hibbits wrote:
>
> > Log:
> > Replace all resource occurrences of '0UL/~0UL' with '0/~0'.
> >
> > Summary:
> > The idea behind this is '~0ul' is well-defined, and casting to uintmax_t,
> > on a
> > 32-bit platform
On Thu, 3 Mar 2016, Justin Hibbits wrote:
On Thu, Mar 3, 2016 at 12:18 AM, Bruce Evans wrote:
On Thu, 3 Mar 2016, Justin Hibbits wrote:
Log:
Replace all resource occurrences of '0UL/~0UL' with '0/~0'.
Summary:
The idea behind this is '~0ul' is well-defined, and casting to uintmax_t,
on a
On Thu, Mar 3, 2016 at 12:18 AM, Bruce Evans wrote:
> On Thu, 3 Mar 2016, Justin Hibbits wrote:
>
>> Log:
>> Replace all resource occurrences of '0UL/~0UL' with '0/~0'.
>>
>> Summary:
>> The idea behind this is '~0ul' is well-defined, and casting to uintmax_t,
>> on a
>> 32-bit platform, will
[Trying again with a corrected E-mail address.]
What does FreeBSD support of the the possible implementation-defined aspects
for signed-integral value representations for C? C++? I ask because of 1's
complement and signed magnitude as reported on below. . .
[I'm not covering signed conversion t
On Thu, 3 Mar 2016, Justin Hibbits wrote:
Log:
Replace all resource occurrences of '0UL/~0UL' with '0/~0'.
Summary:
The idea behind this is '~0ul' is well-defined, and casting to uintmax_t, on a
32-bit platform, will leave the upper 32 bits as 0. The maximum range of a
resource is 0xFFF..
Author: jhibbits
Date: Thu Mar 3 05:07:35 2016
New Revision: 296336
URL: https://svnweb.freebsd.org/changeset/base/296336
Log:
Replace all resource occurrences of '0UL/~0UL' with '0/~0'.
Summary:
The idea behind this is '~0ul' is well-defined, and casting to uintmax_t, on a
32-bit plat
