February 2024 - Boost-users

tommath.h and boost\multiprecision\tommath.hpp
by Helmut Zeisel 28 Feb '24

28 Feb '24

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

2 3

boost::stacktrace::stacktrace AND addr2line
by Foelsche, Peter 19 Feb '24

19 Feb '24

Dear All, Thanks for outstanding quality of boost! I'm using the stacktrace object together with debug info and BOOST_STACKTRACE_USE_ADDR2LINE defined. Would it be possible to cache the output of addr2line assuming that during the lifetime of the calling process the queried executable or shared objects do not change? Thanks Peter

2 2

[boost::interprocess] between Rosetta and native apps - please advice how to fix issue
by Frank G 07 Feb '24

07 Feb '24

We need named IPC between Rosetta and native apps. In boost this seems not compatible, for example with Native app and we are unable to find the "MAP_FNAME" in find_and_construct on the Rosetta process. Works fine when each process is on same arch. " typedef boost::interprocess::managed_shared_memory shared_mem;shared_mem* seg;seg = new shared_mem(boost::interprocess::open_or_create, SHARED_FILENAME, F_MAX_TOTALBUF_SIZE );Img = seg->find_or_construct<imgtype>(MAP_FNAME)(); " Root cause seems to be MemoryAlgorithm and alignment.This has alignment of 16 for Rosetta and 8 for native.The 8 byte shift seems to be the root cause and I can see this when viewing memory. Looking deeper over the last few days we can see this from the difference in frontend size (from MemoryAlgorithm): "boost::interprocess::open_or_create This creates different sized frontend (iset_index 8 or 16)for Native vs Rosetta. frontend is defined from: boost::interprocess::ipcdetail::basic_managed_memory_impl<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family>, boost::interprocess::iset_index, 16> *const Then perform segment->find_or_construct<mtstruct>(MAP_FNAME)(); does not work across arch." Ideally we prefer not to write a bunch of complex custom allocators etc to get this to work with open_or_create and find_or_construct, and hoping there is some simplest solution. Questions: how can we workaround this? Can we force boost::interprocess::open_or_create to use same memory algo for both arch? Or force alignment to 16 for both arch?

1 0