Re: tommath.h and boost\multiprecision\tommath.hpp
Matt Borland via Boost-users <[email protected]> Wed, 28 Feb 2024 10:01:28 +0000
| Newsgroups | gmane.comp.lib.boost.user |
|---|---|
| Message-ID | <t-NUhJGrgk1hJ2bySOXC42LzruShSZjZnzqw43_kAMtO9IRrcyTyK8ez2GPnFEhOAzbrkZq8egQi1aEKHX5NDI6yfmhb3gM2Ft4GaisnS8U=@mattborland.com> |
On Wednesday, February 28th, 2024 at 9:21 AM, Helmut Zeisel via Boost-users <[email protected]> wrote: > > > I tried to use boost muiltiprecision with Visual Studio 2022, 64 bit and got the following error message: > > boost\multiprecision\tommath.hpp(444,36): error C2664: 'mp_err mp_radix_size(const mp_int *,int,size_t *)': cannot convert argument 3 from 'int *' to 'size_t *' > > I used tommath.h from > > https://github.com/libtom/libtommath/blob/develop/tommath.h > > that has (line 583) > > mp_err mp_radix_size(const mp_int *a, int radix, size_t size) MP_WUR; > > but boost\multiprecision\tommath.hpp, lineS 443/444 are > > int s; > detail::check_tommath_result(mp_radix_size(const_cast< ::mp_int>(&m_data), base, &s)); > > > I compared with cygwin, there tommath.h is > > mp_err mp_radix_size(const mp_int *a, int radix, int *size) MP_WUR; > > So I am not sure: do I need some different tommath for Visual Studio 2022, 64 bit, or should boost\multiprecision\tommath.hpp be changed? > > Helmut > _______________________________________________ Helmut, I opened your issue against the library here: https://github.com/boostorg/multiprecision/issues/602. I have Tommath v1.2.1 installed on my system (MacOS ARM64) which has: mp_err mp_radix_size(const mp_int *a, int radix, int *size) MP_WUR; Maybe a new change on develop? If you have a minimal reproducer for your issue that would help as well. Thanks. Matt _______________________________________________ Boost-users mailing list [email protected] https://lists.boost.org/mailman/listinfo.cgi/boost-users
publickey - [email protected] - 0xC1382EAD.asc
(application/pgp-keys, 653 B)
-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEX2wgdBYJKwYBBAHaRw8BAQdAUHOh0KpbZCszhdvKztWj4C6FR1ozMBQE waBi3m2PJHLNK21hdHRAbWF0dGJvcmxhbmQuY29tIDxtYXR0QG1hdHRib3Js YW5kLmNvbT7CjwQQFgoAIAUCX2wgdAYLCQcIAwIEFQgKAgQWAgEAAhkBAhsD Ah4BACEJEFmBWlVCFaWlFiEEwTgurTcoHwbdSbIsWYFaVUIVpaVWuwEA77rm OA4TB6Xxe6q8gI42bEICMhMyZKSMcakz39/djYkBAMJOG+IGQC/d0n3dsl10 Kg/oxX88kFO1oPKn4/XW+ToBzjgEX2wgdBIKKwYBBAGXVQEFAQEHQOsmo6wR UuXRAvFIiqmQkzYrPyvKYKna2z4ZtmnTQMkMAwEIB8J4BBgWCAAJBQJfbCB0 AhsMACEJEFmBWlVCFaWlFiEEwTgurTcoHwbdSbIsWYFaVUIVpaWUJwEA5G0c ZRnG5WGNErI+y90iQrTv02i4Ivhv7twoFcLD/zwA/jKypw+vehE99mEj1/uI EkoDFlNzQZqNldbjRcPyI5UH =462S -----END PGP PUBLIC KEY BLOCK-----
signature.asc
(application/pgp-signature, 249 B)
-----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKACcFgmXfBFkJkFmBWlVCFaWlFiEEwTgurTcoHwbdSbIsWYFaVUIV paUAAJZ6AP4qe2EsDYFmZbaudfovh7PxEwmpMP9Lkyc7e0xGgbXTcgD/Q2cL ZdKiiicE1A4r2fRQXlnfJuJJcNM4zMOmQtVIJAw= =b9qL -----END PGP SIGNATURE-----