From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14748 invoked from network); 31 May 2023 16:58:32 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 31 May 2023 16:58:32 -0000 Received: (qmail 3456 invoked by uid 550); 31 May 2023 16:58:29 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 3409 invoked from network); 31 May 2023 16:58:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:subject:in-reply-to:references:message-id: mime-version:content-transfer-encoding; bh=fcKgIUeYTGW4fjm+S+4OMbnmIvzsclkEjdUyEmbGymY=; b=WKOU/xYHDTcAKb/lGPypfPK39peg3v8UUDs8wX6FxcyrMcN0QMIyNhJr d/Fgo6FgjTyKONkTpz9jsxolPuc+N/NXXvwIwthuv+P1dB/EemJckCU+6 oBw7ZHYKL2f8K0FDBxN+bWwgXzCoBDVhKXGJmmUeK1GwCYtSC+kJzhHhN w=; Authentication-Results: mail3-relais-sop.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=jens.gustedt@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr X-IronPort-AV: E=Sophos;i="6.00,207,1681164000"; d="scan'208";a="57483283" Date: Wed, 31 May 2023 18:58:15 +0200 From: Jens Gustedt To: musl@lists.openwall.com User-Agent: K-9 Mail for Android In-Reply-To: <84a7a59e-afe9-2b63-7039-25f9638cfb0b@ispras.ru> References: <1c8e850ed3190af39b9e3f501d79899d438e7292.1685536608.git.Jens.Gustedt@inria.fr> <20230531142743.GB4163@brightrain.aerifal.cx> <20230531163643.2a382b4a@inria.fr> <20230531144128.GD4163@brightrain.aerifal.cx> <20230531165545.29eb823f@inria.fr> <20230531145724.GF4163@brightrain.aerifal.cx> <20230531170700.65bd9c11@inria.fr> <20230531151406.GG4163@brightrain.aerifal.cx> <20230531173718.3d7d499f@inria.fr> <20230531154043.GH4163@brightrain.aerifal.cx> <20230531175628.168043d2@inria.fr> <84a7a59e-afe9-2b63-7039-25f9638cfb0b@ispras.ru> Message-ID: <47E67930-DACE-4475-86F2-022A0EAA5F30@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: =?US-ASCII?Q?Re=3A_=5Bmusl=5D_=5BC23_128_bit_4/4=5D_C23=3A_implemen?= =?US-ASCII?Q?t_proper_support_for_int128=5Ft_and_uint128=5Ft?= Am 31=2E Mai 2023 18:30:16 MESZ schrieb Alexander Monakov : >=20 > On Wed, 31 May 2023, J=E2=82=91=E2=82=99=E2=82=9B Gustedt wrote: >=20 > > Again, this is not an extension but an optional feature, and this has > > nothing of bleeding edge=2E This is present in compilers since ages, a= nd > > everybody is using their specific ways to go around the restrictions > > of previous C standards=2E >=20 > So, to make sure, by compiler support do you mean __int128 here? yes > It is > not supported on 32-bit platforms neither by GCC nor by LLVM=2E On 64-bi= t > platforms it is piggy-backing on double-word operations support required > for implementing 64-bit 'long long' on 32-bit platforms=2E So what? On the arch where it exist, it is used and useful=2E (And I also = think that implementations improved over the state from 20 years ago that y= ou describe=2E) Nobody is talking about offering it on compilers where there is no support= =2E With the proposed patches this becomes an optional feature with featur= e tests=2E A real improvement for users, that up to now have to guess on th= eir own=2E Jens --=20 Jens Gustedt - INRIA & ICube, Strasbourg, France