From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) by sourceware.org (Postfix) with ESMTPS id 006583858C1F for ; Thu, 15 Jun 2023 06:23:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 006583858C1F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linux.ibm.com Received: from pps.filterd (m0353725.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 35F6CGJ2008813; Thu, 15 Jun 2023 06:23:52 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=pp1; bh=iDsIVRKmtVDN0wKaZUbGqxMHcSbZncfbiViIXcrbdGQ=; b=pi4X3sk+fPnNfnStscLhKo/yFDhIPRe2s1Mi6Q6wZgGhPlGhauO5MiLmYEaoulL/Po+q W4gyzqn+pM0S2NkepksejsM7y7r8I5PIVmRqfc4PJnEP6Joun9sbpkmxPchDUeyhvcOa XMAOE+IWFp/1+FbYIZTRCgs+Krud09pmaNe2rHNIJ2cE0idxdhaWY5zx/zoLQH+EsSDr KEL/iQLL5r9jBrddvVEmBW53giAThpgyWVoqvLI+Ia/XfX2+2wyguNuHVqmcF1ybPPtz hl0NDzLRF1+um3hZwdlGoXhvv6ER1nXnqb14DhXMsvcRQO6oFvzy08v9HGnMMSuNaZW4 wA== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3r7vtcgpwj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Jun 2023 06:23:52 +0000 Received: from m0353725.ppops.net (m0353725.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 35F6CMLQ009286; Thu, 15 Jun 2023 06:23:51 GMT Received: from ppma04ams.nl.ibm.com (63.31.33a9.ip4.static.sl-reverse.com [169.51.49.99]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3r7vtcgpvn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Jun 2023 06:23:51 +0000 Received: from pps.filterd (ppma04ams.nl.ibm.com [127.0.0.1]) by ppma04ams.nl.ibm.com (8.17.1.19/8.17.1.19) with ESMTP id 35F2U7cb021650; Thu, 15 Jun 2023 06:23:49 GMT Received: from smtprelay06.fra02v.mail.ibm.com ([9.218.2.230]) by ppma04ams.nl.ibm.com (PPS) with ESMTPS id 3r4gt53drx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Jun 2023 06:23:49 +0000 Received: from smtpav07.fra02v.mail.ibm.com (smtpav07.fra02v.mail.ibm.com [10.20.54.106]) by smtprelay06.fra02v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 35F6NkAl38994588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 15 Jun 2023 06:23:46 GMT Received: from smtpav07.fra02v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AF47C20043; Thu, 15 Jun 2023 06:23:46 +0000 (GMT) Received: from smtpav07.fra02v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 259AB2004B; Thu, 15 Jun 2023 06:23:44 +0000 (GMT) Received: from [9.177.83.19] (unknown [9.177.83.19]) by smtpav07.fra02v.mail.ibm.com (Postfix) with ESMTP; Thu, 15 Jun 2023 06:23:43 +0000 (GMT) Message-ID: Date: Thu, 15 Jun 2023 14:23:42 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: [PATCH ver 4] rs6000: Add builtins for IEEE 128-bit floating point values Content-Language: en-US To: Carl Love Cc: Segher Boessenkool , Peter Bergner , dje.gcc@gmail.com, gcc-patches@gcc.gnu.org References: <55e5df9a67f6080c3c00fb2e3a15fc404a12d53c.camel@us.ibm.com> From: "Kewen.Lin" In-Reply-To: <55e5df9a67f6080c3c00fb2e3a15fc404a12d53c.camel@us.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: sWWo6_XfE4p39mnh8lxAucOOgUHT7y4K X-Proofpoint-GUID: fowvnUCpznFFOyh2QcaiXlSxtWhcBd8u X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.573,FMLib:17.11.176.26 definitions=2023-06-15_03,2023-06-14_02,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 phishscore=0 lowpriorityscore=0 suspectscore=0 mlxlogscore=999 clxscore=1015 priorityscore=1501 mlxscore=0 spamscore=0 bulkscore=0 malwarescore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2305260000 definitions=main-2306150051 X-Spam-Status: No, score=-11.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,GIT_PATCH_0,KAM_SHORT,NICE_REPLY_A,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Carl, on 2023/6/15 04:37, Carl Love wrote: > Kewen, GCC maintainers: > > Version 4, added missing cases for new xxexpqp, xsxexpdp and xsxsigqp > cases to rs6000_expand_builtin. Merged the new define_insn definitions > with the existing definitions. Renamed the builtins by removing the > __builtin_ prefix from the names. Fixed the documentation for the > builtins. Updated the test files to check the desired instructions > were generated. Retested patch on Power 10 with no regressions. > > Version 3, was able to get the overloaded version of scalar_insert_exp > to work and the change to xsxexpqp_f128_ define instruction to > work with the suggestions from Kewen. > > Version 2, I have addressed the various comments from Kewen. I had > issues with adding an additional overloaded version of > scalar_insert_exp with vector arguments. The overload infrastructure > didn't work with a mix of scalar and vector arguments. I did rename > the __builtin_insertf128_exp to __builtin_vsx_scalar_insert_exp_qp make > it similar to the existing builtin. I also wasn't able to get the > suggested merge of xsxexpqp_f128_ with xsxexpqp_ to work so > I left the two simpler definitiions. > > The patch add three new builtins to extract the significand and > exponent of an IEEE float 128-bit value where the builtin argument is a > vector. Additionally, a builtin to insert the exponent into an IEEE > float 128-bit vector argument is added. These builtins were requested > since there is no clean and optimal way to transfer between a vector > and a scalar IEEE 128 bit value. > > The patch has been tested on Power 10 with no regressions. Please let > me know if the patch is acceptable or not. Thanks. I'd suggest you to test this on P9 BE as well to ensure the test case to work well on BE too. > > Carl > > > ---------------------------------------- > rs6000: Add builtins for IEEE 128-bit floating point values > > Add support for the following builtins: > > __vector unsigned long long int scalar_extract_exp_to_vec (__ieee128); > __vector unsigned __int128 scalar_extract_sig_to_vec (__ieee128); > __ieee128 scalar_insert_exp (__vector unsigned __int128, > __vector unsigned long long); > > These builtins were requesed since there is no clean and performant way to s/requesed/requested/ > transfer a value from a vector type and scalar type, despite the fact Describe it oppositely? As the related existing bifs returns scalar type, the users want them in vector type, so it's "from scalar type to vector type"? > that they both reside in vector registers. the fact is the related hardware insns have vsx registers destination. > > gcc/ > * config/rs6000/rs6000-builtin.cc (rs6000_expand_builtin): > Rename CCDE_FOR_xsxexpqp_tf to CODE_FOR_xsxexpqp_tf_di. > Rename CODE_FOR_xsxexpqp_kf to CODE_FOR_xsxexpqp_kf_di. > (CODE_FOR_xsxexpqp_kf_v2di, CODE_FOR_xsxsigqp_kf_v1ti, > CODE_FOR_xsiexpqp_kf_v2di ): Add case statements. unnecessary tab. > * config/rs6000/rs6000-buildin.def (__builtin_extractf128_exp, > __builtin_extractf128_sig, __builtin_insertf128_exp): Add new > builtin definitions. > Rename xsxexpqp_kf, xsxsigqp_kf, xxsiexpqp_kf to xsexpqp_kf_di, typo, xxsiexpqp_kf => xsiexpqp_kf > xsxsigqp_kf_ti, xsiexpqp_kf_di respectively. > * config/rs6000/rs6000-c.cc (altivec_resolve_overloaded_builtin): > Add else if for MODE_VECTOR_INT. Update comments. May be better with "Update RS6000_OVLD_VEC_VSIE handling for MODE_VECTOR_INT which is used for newly added overloaded instance"? > * config/rs6000/rs6000-overload.def > (__builtin_vec_scalar_insert_exp): Add new overload definition with > vector arguments. > (scalar_extract_exp_to_vec, scalar_extract_sig_to_vec): New > odverloaded definitions. s/odverloaded/overloaded/ > * config/vsx.md (VSEEQP_DI, VSESQP_TI): New mode iterators. > (VSEEQP_DI_base): New mode attribute definition. > Rename xsxexpqp_ to sxexpqp__. > Rename xsxsigqp_ to xsxsigqp__. > Rename xsiexpqp_ to xsiexpqp__. > (xsxsigqp_f128_, xsiexpqpf_f128_): Add define_insn for > new builtins. > * doc/extend.texi (__builtin_extractf128_exp, > __builtin_extractf128_sig): Add documentation for new builtins. > (scalar_insert_exp): Add new overloaded builtin definition. > > gcc/testsuite/ > * gcc.target/powerpc/bfp/extract-exp-1.c: New test case. > * gcc.target/powerpc/bfp/extract-sig-1.c: New test case. > * gcc.target/powerpc/bfp/insert-exp-1.c: New test case. May be better just with the existing base name and increasing number: extract-exp-1.c => scalar-extract-exp-8.c extract-sig-1.c => scalar-extract-sig-8.c insert-exp-1.c => scalar-insert-exp-16.c > --- > gcc/config/rs6000/rs6000-builtin.cc | 21 +++-- > gcc/config/rs6000/rs6000-builtins.def | 15 ++- > gcc/config/rs6000/rs6000-c.cc | 10 +- > gcc/config/rs6000/rs6000-overload.def | 10 ++ > gcc/config/rs6000/vsx.md | 26 +++-- > gcc/doc/extend.texi | 21 ++++- > .../gcc.target/powerpc/bfp/extract-exp-1.c | 53 +++++++++++ > .../gcc.target/powerpc/bfp/extract-sig-1.c | 60 ++++++++++++ > .../gcc.target/powerpc/bfp/insert-exp-1.c | 94 +++++++++++++++++++ > 9 files changed, 284 insertions(+), 26 deletions(-) > create mode 100644 gcc/testsuite/gcc.target/powerpc/bfp/extract-exp-1.c > create mode 100644 gcc/testsuite/gcc.target/powerpc/bfp/extract-sig-1.c > create mode 100644 gcc/testsuite/gcc.target/powerpc/bfp/insert-exp-1.c > > diff --git a/gcc/config/rs6000/rs6000-builtin.cc b/gcc/config/rs6000/rs6000-builtin.cc > index 534698e7d3e..a8f291c6a72 100644 > --- a/gcc/config/rs6000/rs6000-builtin.cc > +++ b/gcc/config/rs6000/rs6000-builtin.cc > @@ -3326,17 +3326,26 @@ rs6000_expand_builtin (tree exp, rtx target, rtx /* subtarget */, > case CODE_FOR_fmakf4_odd: > icode = CODE_FOR_fmatf4_odd; > break; > - case CODE_FOR_xsxexpqp_kf: > - icode = CODE_FOR_xsxexpqp_tf; > + case CODE_FOR_xsxexpqp_kf_di: > + icode = CODE_FOR_xsxexpqp_tf_di; > break; > - case CODE_FOR_xsxsigqp_kf: > - icode = CODE_FOR_xsxsigqp_tf; > + case CODE_FOR_xsxexpqp_kf_v2di: > + icode = CODE_FOR_xsxexpqp_tf_v2di; > + break; > + case CODE_FOR_xsxsigqp_kf_ti: > + icode = CODE_FOR_xsxsigqp_tf_ti; > + break; > + case CODE_FOR_xsxsigqp_kf_v1ti: > + icode = CODE_FOR_xsxsigqp_tf_v1ti; > break; > case CODE_FOR_xststdcnegqp_kf: > icode = CODE_FOR_xststdcnegqp_tf; > break; > - case CODE_FOR_xsiexpqp_kf: > - icode = CODE_FOR_xsiexpqp_tf; > + case CODE_FOR_xsiexpqp_kf_di: > + icode = CODE_FOR_xsiexpqp_tf_di; > + break; > + case CODE_FOR_xsiexpqp_kf_v2di: > + icode = CODE_FOR_xsiexpqp_tf_v2di; > break; > case CODE_FOR_xsiexpqpf_kf: > icode = CODE_FOR_xsiexpqpf_tf; > diff --git a/gcc/config/rs6000/rs6000-builtins.def b/gcc/config/rs6000/rs6000-builtins.def > index 638d0bc72ca..6623cb8195d 100644 > --- a/gcc/config/rs6000/rs6000-builtins.def > +++ b/gcc/config/rs6000/rs6000-builtins.def > @@ -2901,20 +2901,29 @@ > fpmath double __builtin_truncf128_round_to_odd (_Float128); > TRUNCF128_ODD trunckfdf2_odd {} > > + vull __builtin_scalar_extract_exp_to_vec (_Float128); > + EEXPKF xsxexpqp_kf_v2di {} Since you have added one entry in overload.def for this, I think it's better to name this as __builtin_**vsx**_scalar_extract_exp_to_vec just like the others. And sorry for nit-picking, the related bif has the id VSEEQP, could we use VSEEQPV for the id here? And move this entry just after its related __builtin_vsx_scalar_extract_expq. > + > + vuq __builtin_scalar_extract_sig_to_vec (_Float128); > + ESIGKF xsxsigqp_kf_v1ti {} > + Similar comments like above applied for this one. > const signed long long __builtin_vsx_scalar_extract_expq (_Float128); > - VSEEQP xsxexpqp_kf {} > + VSEEQP xsxexpqp_kf_di {} > > const signed __int128 __builtin_vsx_scalar_extract_sigq (_Float128); > - VSESQP xsxsigqp_kf {} > + VSESQP xsxsigqp_kf_ti {} > > const _Float128 __builtin_vsx_scalar_insert_exp_q (unsigned __int128, \ > unsigned long long); > - VSIEQP xsiexpqp_kf {} > + VSIEQP xsiexpqp_kf_di {} > > const _Float128 __builtin_vsx_scalar_insert_exp_qp (_Float128, \ > unsigned long long); > VSIEQPF xsiexpqpf_kf {} > > + const _Float128 __builtin_vsx_scalar_insert_exp_vqp (vuq, vull); > + VSIEQPV xsiexpqp_kf_v2di {} > + > const signed int __builtin_vsx_scalar_test_data_class_qp (_Float128, \ > const int<7>); > VSTDCQP xststdcqp_kf {} > diff --git a/gcc/config/rs6000/rs6000-c.cc b/gcc/config/rs6000/rs6000-c.cc > index 8555174d36e..11060f697db 100644 > --- a/gcc/config/rs6000/rs6000-c.cc > +++ b/gcc/config/rs6000/rs6000-c.cc > @@ -1929,11 +1929,15 @@ altivec_resolve_overloaded_builtin (location_t loc, tree fndecl, > 128-bit variant of built-in function. */ > if (GET_MODE_PRECISION (arg1_mode) > 64) > { > - /* If first argument is of float variety, choose variant > - that expects __ieee128 argument. Otherwise, expect > - __int128 argument. */ > + /* If first argument is of float variety, choose the variant that > + expects __ieee128 argument. If the first argument is vector > + int, choose the variant that expects vector unsigned > + __int128 argument. Otherwise, expect scalar __int128 argument. > + */ > if (GET_MODE_CLASS (arg1_mode) == MODE_FLOAT) > instance_code = RS6000_BIF_VSIEQPF; > + else if (GET_MODE_CLASS (arg1_mode) == MODE_VECTOR_INT) > + instance_code = RS6000_BIF_VSIEQPV; > else > instance_code = RS6000_BIF_VSIEQP; > } > diff --git a/gcc/config/rs6000/rs6000-overload.def b/gcc/config/rs6000/rs6000-overload.def > index c582490c084..1c503a4b3d3 100644 > --- a/gcc/config/rs6000/rs6000-overload.def > +++ b/gcc/config/rs6000/rs6000-overload.def > @@ -4515,6 +4515,16 @@ > VSIEQP > _Float128 __builtin_vec_scalar_insert_exp (_Float128, unsigned long long); > VSIEQPF > + _Float128 __builtin_vec_scalar_insert_exp (vuq, vull); > + VSIEQPV > + > +[VEC_VSEEV, scalar_extract_exp_to_vec, __builtin_scalar_extract_exp_to_vector] Thanks for adding this, to make it more consistent with the existing others, I think the latter name would be better with __builtin_**vec**_scalar_extract_exp_to_vector. > + vull __builtin_scalar_extract_exp_to_vector (_Float128); > + EEXPKF Need to update this bif id accordingly if the one in rs6000-buildin.def changes. > + > +[VEC_VSESV, scalar_extract_sig_to_vec, __builtin_scalar_extract_sig_to_vector] > + vuq __builtin_scalar_extract_sig_to_vector (_Float128); > + ESIGKF > Ditto. > [VEC_VSTDC, scalar_test_data_class, __builtin_vec_scalar_test_data_class] > unsigned int __builtin_vec_scalar_test_data_class (float, const int); > diff --git a/gcc/config/rs6000/vsx.md b/gcc/config/rs6000/vsx.md > index 7d845df5c2d..bb19b5ef170 100644 > --- a/gcc/config/rs6000/vsx.md > +++ b/gcc/config/rs6000/vsx.md > @@ -396,6 +396,10 @@ > V4SF > V2DF > V2DI]) > +(define_mode_iterator VSEEQP_DI [V2DI DI]) Since you hoist this to one centralized place, I guess it may be better to name it more general, like: V2DI_DI. > +(define_mode_iterator VSESQP_TI [V1TI TI]) VEC_TI matches the requirement here. > +(define_mode_attr VSEEQP_DI_base [(V2DI "V1TI") > + (DI "TI")]) As above, may be better with name DI_to_TI. > > (define_mode_attr VM3_char [(V2DI "d") > (V4SI "w") > @@ -5008,9 +5012,10 @@ > ;; ISA 3.0 Binary Floating-Point Support > > ;; VSX Scalar Extract Exponent Quad-Precision > -(define_insn "xsxexpqp_" > - [(set (match_operand:DI 0 "altivec_register_operand" "=v") > - (unspec:DI [(match_operand:IEEE128 1 "altivec_register_operand" "v")] > +(define_insn "xsxexpqp__" > + [(set (match_operand:VSEEQP_DI 0 "altivec_register_operand" "=v") > + (unspec:VSEEQP_DI > + [(match_operand:IEEE128 1 "altivec_register_operand" "v")] > UNSPEC_VSX_SXEXPDP))] > "TARGET_P9_VECTOR" > "xsxexpqp %0,%1" > @@ -5026,9 +5031,10 @@ > [(set_attr "type" "integer")]) > > ;; VSX Scalar Extract Significand Quad-Precision > -(define_insn "xsxsigqp_" > - [(set (match_operand:TI 0 "altivec_register_operand" "=v") > - (unspec:TI [(match_operand:IEEE128 1 "altivec_register_operand" "v")] > +(define_insn "xsxsigqp__" > + [(set (match_operand:VSESQP_TI 0 "altivec_register_operand" "=v") > + (unspec:VSESQP_TI [(match_operand:IEEE128 1 > + "altivec_register_operand" "v")] > UNSPEC_VSX_SXSIG))] > "TARGET_P9_VECTOR" > "xsxsigqp %0,%1" > @@ -5055,10 +5061,12 @@ > [(set_attr "type" "vecmove")]) > > ;; VSX Scalar Insert Exponent Quad-Precision > -(define_insn "xsiexpqp_" > +(define_insn "xsiexpqp__" > [(set (match_operand:IEEE128 0 "altivec_register_operand" "=v") > - (unspec:IEEE128 [(match_operand:TI 1 "altivec_register_operand" "v") > - (match_operand:DI 2 "altivec_register_operand" "v")] > + (unspec:IEEE128 [(match_operand: 1 > + "altivec_register_operand" "v") > + (match_operand:VSEEQP_DI 2 > + "altivec_register_operand" "v")] > UNSPEC_VSX_SIEXPQP))] > "TARGET_P9_VECTOR" > "xsiexpqp %0,%1,%2" > diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi > index e426a2eb7d8..6da7ae9d94c 100644 > --- a/gcc/doc/extend.texi > +++ b/gcc/doc/extend.texi > @@ -19724,6 +19724,10 @@ double scalar_insert_exp (double significand, unsigned long long int exponent); > ieee_128 scalar_insert_exp (unsigned __int128 significand, > unsigned long long int exponent); > ieee_128 scalar_insert_exp (ieee_128 significand, unsigned long long int exponent); > +vector ieee_128 scalar_insert_exp (vector unsigned __int128, > + vector unsigned long long); > +vector unsigned long long scalar_extract_exp_to_vec (ieee_128); > +vector unsigned __int128 scalar_extract_sig_to_vec (ieee_128); > > int scalar_cmp_exp_gt (double arg1, double arg2); > int scalar_cmp_exp_lt (double arg1, double arg2); > @@ -19771,11 +19775,18 @@ of the result are composed of the least significant 11 bits of the > > When supplied with a 128-bit first argument, the > @code{scalar_insert_exp} built-in function returns a quad-precision > -ieee floating point value. The sign bit of the result is copied from > -the most significant bit of the @code{significand} argument. > -The significand and exponent components of the result are composed of > -the least significant 15 bits of the @code{exponent} argument and the > -least significant 112 bits of the @code{significand} argument respectively. > +ieee floating point value if the two arguments were scalar. If the two > +arguments are vectors, the retun value is a vector ieee floating point value. s/retun/return/ > +The sign bit of the result is copied from the most significant bit of the > +@code{significand} argument. The significand and exponent components of the > +result are composed of the least significant 15 bits of the @code{exponent} > +argument and the least significant 112 bits of the @code{significand} argument > +respectively. The @code{exponent} now is a vector and has two elements, you should note which element matters here, element zero on big-endian while element one on little-endian will be used. Since this document quoted both @code{significand} and @code{significand}, the above prototype should have the argument name as well. :) +vector ieee_128 scalar_insert_exp (vector unsigned __int128 significand, + vector unsigned long long exponent); The others look good to me, thanks! BR, Kewen