Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Top 10 most common hard skills listed on resumes... Date: Tue, 10 Sep 2024 12:49:44 -0700 Organization: None to speak of Lines: 22 Message-ID: <871q1r1e7b.fsf@nosuchdomain.example.com> References: <878qw13a40.fsf@nosuchdomain.example.com> <874j6p34df.fsf@nosuchdomain.example.com> <20240909114553.226@kylheku.com> <20240909152336.398@kylheku.com> <86bk0viwml.fsf@linuxsc.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Tue, 10 Sep 2024 21:49:45 +0200 (CEST) Injection-Info: dont-email.me; posting-host="29df7bbfeaa4d6ddeb7fdca1349b4e93"; logging-data="3288061"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+3JN4qg+EjCWsrzzdjvXmE" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:+IMFlsYD/w6/Cc6MhaGbxIXj+q0= sha1:nFPK5bhgbgEAStsN2VPeP9QBJjg= Bytes: 2420 Tim Rentsch 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. __int128 is treated as a keyword. __int128_t appears to be a predefined identifier; it's visible even if no headers are included. __int128 and __int128_t are compatible types, probably the same type. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com void Void(void) { Void(); } /* The recursive call of the void */