From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@libc.org>
Subject: Re: [musl] [C23 128 bit 4/4] C23: implement proper support for int128_t and uint128_t
Date: Wed, 31 May 2023 19:30:16 +0300 (MSK) [thread overview]
Message-ID: <84a7a59e-afe9-2b63-7039-25f9638cfb0b@ispras.ru> (raw)
In-Reply-To: <20230531175628.168043d2@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Wed, 31 May 2023, Jₑₙₛ Gustedt wrote:
> Again, this is not an extension but an optional feature, and this has
> nothing of bleeding edge. This is present in compilers since ages, and
> everybody is using their specific ways to go around the restrictions
> of previous C standards.
So, to make sure, by compiler support do you mean __int128 here? It is
not supported on 32-bit platforms neither by GCC nor by LLVM. On 64-bit
platforms it is piggy-backing on double-word operations support required
for implementing 64-bit 'long long' on 32-bit platforms.
Alexander
next prev parent reply other threads:[~2023-05-31 16:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 14:15 [musl] [C23 128 bit 0/4] implement the library part of 128 bit support Jens Gustedt
2023-05-31 14:15 ` [musl] [C23 128 bit 1/4] add an emulation for 128 bit arithmetic as needed for C library support Jens Gustedt
2023-05-31 14:15 ` [musl] [C23 128 bit 2/4] C23: implement w128 and wf128 support for printf Jens Gustedt
2023-05-31 14:15 ` [musl] [C23 128 bit 3/4] C23: implement w128 and wf128 for scanf and similar Jens Gustedt
2023-05-31 14:15 ` [musl] [C23 128 bit 4/4] C23: implement proper support for int128_t and uint128_t Jens Gustedt
2023-05-31 14:27 ` Rich Felker
2023-05-31 14:29 ` Rich Felker
2023-05-31 14:36 ` Jₑₙₛ Gustedt
2023-05-31 14:41 ` Rich Felker
2023-05-31 14:55 ` Jₑₙₛ Gustedt
2023-05-31 14:57 ` Rich Felker
2023-05-31 15:07 ` Jₑₙₛ Gustedt
2023-05-31 15:14 ` Rich Felker
2023-05-31 15:37 ` Jₑₙₛ Gustedt
2023-05-31 15:40 ` Rich Felker
2023-05-31 15:56 ` Jₑₙₛ Gustedt
2023-05-31 16:30 ` Alexander Monakov [this message]
2023-05-31 16:58 ` Jens Gustedt
2023-05-31 17:03 ` Rich Felker
2023-05-31 17:09 ` Alexander Monakov
2023-06-01 7:24 ` Jₑₙₛ Gustedt
2023-05-31 14:42 ` Jₑₙₛ Gustedt
2023-05-31 14:47 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84a7a59e-afe9-2b63-7039-25f9638cfb0b@ispras.ru \
--to=amonakov@ispras.ru \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).