Path: csiph.com!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: Top 10 most common hard skills listed on resumes...
Date: Sat, 14 Sep 2024 15:13:56 -0700
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <86cyl5evdn.fsf@linuxsc.com>
References: <vab101$3er$1@reader1.panix.com> <vbekut$1kd24$1@paganini.bofh.team> <vbepcb$q6p2$1@dont-email.me> <vbgb5q$1ruv8$1@paganini.bofh.team> <vbhbbb$1blt4$1@dont-email.me> <vbipp5$24kl5$1@paganini.bofh.team> <vbk0d9$1tajm$1@dont-email.me> <vbkpfc$27l2o$1@paganini.bofh.team> <vbl3am$228vv$1@dont-email.me> <vblfgb$2dkij$1@paganini.bofh.team> <878qw13a40.fsf@nosuchdomain.example.com> <vbll6l$2dpn7$2@paganini.bofh.team> <874j6p34df.fsf@nosuchdomain.example.com> <vbn79l$2g9i6$1@paganini.bofh.team> <vbn9e1$2fqep$1@dont-email.me> <vbnboc$2g0vc$2@dont-email.me> <20240909114553.226@kylheku.com> <vbngrb$2gvrs$1@dont-email.me> <20240909152336.398@kylheku.com> <86bk0viwml.fsf@linuxsc.com> <871q1r1e7b.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Sun, 15 Sep 2024 00:13:57 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="393c6de94aad5c3a9db23639212fcd5c"; logging-data="1790079"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19rXQeuGipH6wJRN2lFbg2bMLxxQKffuSY="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:rsN4HJKVCXtBZRuObg+imyaUfU8= sha1:7ZfIA5Gc7Q725Y1qJ21dzBP1vNo=
Xref: csiph.com comp.lang.c:388396

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:

> Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
> [...]
>
>> Assuming all that is right, I recommend
>>
>>     typedef  __uint128_t  U128;
>>     typedef   __int128_t  S128;
>>
>> which works in both gcc and clang (I don't know yet about
>> Visual Studio).
>
> The documented names are `__int128` and `unsigned __int128`.
>
> Both gcc and clang do recognize `__int128_t` and `__uint128_t`,
> but I wouldn't recommend relying on an undocumented feature.

Both gcc and clang recognized __[u]int128_t in earlier versions
than they did __int128.  The __[u]int128_t types are also
recognized by the Intel compiler.

> __int128 is treated as a keyword.

That's another reason to prefer __[u]int128_t types.