[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 128-bit uid_t
From: |
Bastien ROUCARIES |
Subject: |
Re: 128-bit uid_t |
Date: |
Sun, 11 Sep 2011 18:44:11 +0200 |
On Sun, Sep 11, 2011 at 6:41 PM, Bastien ROUCARIES
<address@hidden> wrote:
> n Sun, Sep 11, 2011 at 6:33 PM, Paul Eggert <address@hidden> wrote:
>> On 09/11/11 08:14, Bastien ROUCARIES wrote:
>>> gcc has it : http://gcc.gnu.org/onlinedocs/gcc/_005f_005fint128.html
>>> (at least for 64bits)
>>
>> I'd be leery of any attempt to define a system type wider than
>> intmax_t.
>
> For sure but we could override intmax_t, intmax_t is defined at libc
> level not at compiler level.
>
>>Too many things will break. It might be OK to use
>> __int128 for specialized internal purposes (cryptography comes
>> to mind), but not for common external interfaces such as uid_t.
Cert document int use for 128bits so it is used
https://www.securecoding.cert.org/confluence/display/cplusplus/INT15-CPP.+Use+intmax_t+or+uintmax_t+for+formatted+IO+on+programmer-defined+integer+types
> For windows it is the only solution due to microsoft uuid scheme.
>
> Bastien
>
>>
>
Re: msvc port: ensure pid_t is defined, Bruno Haible, 2011/09/20