- Boost-users - lists.stage.boost.cppalliance.org

Possibility to increase boost/multiprecision/mpfr precision.
by Ivo Celmans 28 Dec '25

28 Dec '25

Hello, is it possible to make boost/multiprecision/mpfr work with more than 4294967 decimal digits of precision. I understand that it comes from the unsigned type, but is it possible to adapt it to uint64_t for example? I'm experimenting with headers, but since I've been using multiprecision for a relatively short time, I don't fully understand how the wrapper works and where the dependencies are. I apologize if the question sounds silly, I'm c++ enthusiast. Best regards, Ivo

1 0

boost fibers concurrency
by amit sehas 18 Dec '25

18 Dec '25

HI, I have just started utilizing boost fibers and am completely confused about its conditional variable concurrency behavior. Boost fibers provide the following example for using conditional variables: void wait_for_data_to_process() { { std::unique_lock< boost::fibers::mutex > lk( mtx); while ( ! data_ready) { cond.wait( lk); } } // release lk process_data(); } void prepare_data_for_processing() { retrieve_data(); prepare_data(); { std::unique_lock< boost::fibers::mutex > lk( mtx); data_ready = true; } cond.notify_one(); } But when we do the above we see that the fibers end up running into std::unique_lock waits in system calls sched_yield and futex. We are possibly invoking above concurrency primitives among multiple OS threads. We want to avoid system calls in the fibers. strace outputs are as below: futex(0x7ff4f4005160, FUTEX_WAKE_PRIVATE, 1) = 0 > /usr/lib64/libc.so.6(__GI___lll_lock_wake+0x17) [0x87777] > /usr/lib64/libc.so.6(__GI___pthread_mutex_unlock_usercnt+0x94) [0x8f2d4] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::algo::round_robin::notify()+0x24) [0x73f4] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::context::wake(unsigned long)+0x29) [0xaac9] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::wait_queue::notify_one()+0x40) [0xbca0] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::mutex::unlock()+0x31) [0xc151] sched_yield() = 0 > /usr/lib64/libc.so.6(__sched_yield+0xb) [0xf3d5b] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::detail::spinlock_ttas::lock()+0xd4) [0x9044] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::mutex::lock()+0x28) [0xc198] Apparently even scheduling a fiber seems to run into lock waits, not sure why scheduling a fiber would block: sched_yield() = 0 > /usr/lib64/libc.so.6(__sched_yield+0xb) [0xf3d5b] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::detail::spinlock_ttas::lock()+0xd4) [0x9044] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::scheduler::remote_ready2ready_()+0x33) [0xd353] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::scheduler::dispatch()+0x50) [0xd4e0] > /usr/local/lib/libboost_fiber.so.1.85.0(boost::fibers::dispatcher_context::run_(boost::context::fiber&&)+0xd) [0xb46d] > /usr/local/lib/libboost_fiber.so.1.85.0(void boost::context::detail::fiber_entry<boost::context::detail::fiber_record<boost::context::fiber, boost::fibers::stack_allocator_wrapper, std::_Bind<boost::context::fiber (boost::fibers::dispatcher_context::*(boost::fibers::dispatcher_context*, std::_Placeholder<1>))(boost::context::fiber&&)> > >(boost::context::detail::transfer_t)+0x3a) [0xb4ca] > /usr/local/lib/libboost_context.so.1.85.0(make_fcontext+0x2e) [0x117e] > No DWARF information found We want to avoid all system calls in the fibers to avoid their performance impact, we are confused why the examples provided by boost fibers are running into system calls. Any help is greatly appreciated ... regards -Amit

1 0

[release] Boost 1.90.0
by Marshall Clow 10 Dec '25

10 Dec '25

Release 1.90.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. The release contains one new library: * OpenMethod: Open-(multi-)methods in C++17 and above, from Jean-Louis Leroy. as well as numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.90.0> You can also download directly from: <https://archives.boost.io/release/1.90.0/source/> To install this release on your system, see <https://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. -- The Boost Release Team Marshall Clow, Glen Fernandes, Ion Gaztañaga

1 0

b2 --show-libraries
by Keith Bennett 23 Nov '25

23 Nov '25

Hi guys, Why does `b2 --show-libraries` not show the libraries and exit as --help says it should? I am using boostorg/boost 02b24152984db5f8291778699f87a24dfce49aca, and also see the same behavior on tag boost-1.89.0. It instead goes on to build everything. That's opposite of the --help documentation. Is there not a unit test for this basic feature??? How many other basic features don't have unit tests? How do I just use cmake add_subdirectory(boost) from the boostorg/boost repo? I'm stuck trying to use externalproject_add I just need to build static libraries for packages, and want to have a loop in cmake that does --without-<library> for all of the libraries that I don't depend on. Or, even better, let CMake handle all of the dependencies for any boost libs that depend on each other, if I depend on one of them -- Keith Bennett

2 2

[regex] PR #263 - Fix for MSVC static analysis warning C33010 in get_default_error_string
by Phil Deets 22 Nov '25

22 Nov '25

Hello, I've submitted a PR to fix a static analysis warning in Boost.Regex: https://github.com/boostorg/regex/pull/263 - return (n > ::boost::regex_constants::error_unknown) ? s_default_error_messages[::boost::regex_constants::error_unknown] : s_default_error_messages[n]; + typedef typename std::make_unsigned<regex_constants::error_type>::type unsigned_type; + return (static_cast<unsigned_type>(n) > ::boost::regex_constants::error_unknown) ? s_default_error_messages[::boost::regex_constants::error_unknown] : s_default_error_messages[n]; The function get_default_error_string() in regex_traits_defaults.hpp<https://github.com/boostorg/regex/blob/develop/include/boost/regex/v5/regex…> triggers warning C33010 (unchecked lower bound for enum used as index)<https://learn.microsoft.com/en-us/cpp/code-quality/c33010?view=msvc-170>. There are regulations that require the Windows product to address all occurrences of this warning in any open-source code pulled into the Windows repository. I'm addressing this in the short term by using a Vcpkg overlay port to apply the patch from my PR, but I would like to upstream the fix so I can switch back to the default Vcpkg port for Boost in the future once the fix is released. The fix simply casts the enum value to an unsigned type before doing a bounds check. This ensures that negative values are treated as large positive values in the comparison so they will be detected to be out of bounds. I used a typedef with std::make_unsigned for the type used in the cast. This was done to be consistent with similar code farther up in the file in the is_extended function. Thanks, Phil

1 0

Cmake 4.1
by schoch+boost.org＠starnet.com 21 Nov '25

21 Nov '25

I'm having trouble getting cmake 4.1 to work with boost 1.88. I set the cmake BOOST_ROOT variable to C:\boost_1_88_0 and when my CMakeLists.txt file calls find_package(Boost REQUIRED) it successfully finds the file C:\boost_1_88_0\tools\cmake\config\BoostConfig.cmake, but when that file calls find_package(boost_headers ...) cmake fails, saying it can't find boost_headers-config.cmake, even though I can find that file deep under the C:\boost_1_88_0 directory. Is there an easy way to get boost to work with cmake 4.1?

5 6

Boost.Python - registration for multiple modules only works with dynamic linking?
by Andrej 17 Nov '25

17 Nov '25

Hi! I've stumbled upon `TypeError: No to_python (by-value) converter found for C++ type: class MyClass` kind of error and trying to debug it I came to the conclusion in the thread subject and wanted to verify if I'm not missing something, since I'm not very familar with Boost. So let's say there is `libA` that defines `MyClass` and there's a `libB` that's using it (e.g.. it has `MyClass produce_my_class()`). If `libA` and `libB` are statically linked against Boost.Python, then using `libB` method fails to find a converter (code snippet is below). If I link `libA` and `libB` against shared Boost.Python library, then the issue is resolved. I assume registration is kind of happen *per-Boost.Python-static-instance*, not *per-process*? What's the common practice for this? E.g. let's say there's an independant math library `Math` and it's using Boost.Python. For it to be distributable it typically would statically link Boost.Python. Then there's another library `Geometry` that's trying to use `Math` using Boost.Python bindings. Then the only way it would be able find the converters, if it redefines them? ```python import libA print(libA.MyClass(25)) # <libA.MyClass object at 0x00000199048BC270> import libB print(libB.produce_my_class(25)) # Traceback (most recent call last): # File "<string>", line 1, in <module> # TypeError: No to_python (by-value) converter found for C++ type: class MyClass ```

1 0

Re: [asio-users] boost::asio and seccomp
by Vinícius dos Santos Oliveira 17 Nov '25

17 Nov '25

Em seg., 17 de nov. de 2025 às 13:09, Marek Küthe <m-k-mailling-list(a)mk16.de> escreveu: > Hello, Hi Marek, I have lots of experience with containerization & sandboxing on Linux (and FreeBSD), but very few people to talk to about it (which I do miss more of). Let's keep in contact after I try to help answer your questions. > I would like to make my program more secure under Linux with seccomp. > My question is: how can I query which backend boost::asio uses (epoll, > select, etc.)? Boost.Asio doesn't have fallback logic. You choose which backend to use at compile time by defining macros. Given most vendors disable io_uring nowadays[1], the ideal implementation would not work as Boost.Asio does. The ideal implementation would have fallback logic and try io_uring first. This would also help with sandboxes because seccomp is a terrible model to secure io_uring in capability sandboxes (io_uring communicates with the kernel through message writes, but seccomp only filters syscalls). So if Boost.Asio had fallback logic your application would be able to fork the process, and disable io_uring. On the forked process, Boost.Asio could use epoll while the parent process would use io_uring. That's not possible today. Landlock is a promising new Linux approach that won't ever replace seccomp, but has the potential to secure some interfaces that seccomp can't. Until Landlock is mature and more complete, we have to do stuff such as avoiding io_uring entirely within sandboxes. For Boost.Asio this means using the epoll backend. > I would also like to know which system calls boost::asio > uses for which Linux backend. io_uring doesn't use syscalls so there's no point in filtering syscalls to secure io_uring. For the epoll backend, everyone does basically the same things. Just go through the list of syscalls and enable everything epoll-related. You can look at Kafel for an easy to use language to define seccomp policies. I wrote a few policy groups if you're interested. The only weird thing about Boost.Asio is that it still relies on the ancient'n'fragile FIONBIO[2] instead of fcntl/O_NONBLOCK by default (and MSG_DONTWAIT when available to save syscalls/performance). I complained to Chris until he fixed almost all of my complaints. Nowadays you can use Boost.Asio in many models of capability sandboxes, but not all. The only missing piece is MSG_DONTWAIT which matters to avoid DoS when file descriptors are shared among untrusted processes (necessary for capability sandboxes). I wrote a very detailed article explaining how to develop sandboxes for Linux and FreeBSD, but I suspect only 2 people have actually read the whole thing: https://blog.emilua.org/2025/01/12/software-sandboxing-basics/ The described model is implemented in Emilua which is a runtime (similar to NodeJS) for LuaJIT using Boost.Asio (you can also configure it to use the standalone version of ASIO if you want). Emilua is also a container runtime. You can prototype stuff quickly in Lua using Emilua and implement a high-performance version in pure C++ later if the need arises. That's the last demo I made for Emilua: https://www.youtube.com/watch?v=anu-onpDMBc I'm now keeping in contact with Matthew Flatt to implement sandboxes for Racket. However Racket doesn't use Boost.Asio. I'm also designing a thing to more easily implement sandboxes in C++, but it's still too soon to show this work. I've tried to collaborate with JS runtime developers to implement sandboxes too, but every time I've left these meetings frustrated. JS guys have no ambition at all. They only want to mirror what NodeJS already does (and perhaps do the same stuff but only slightly faster). I have no intention to collaborate with JS communities again. I want to collaborate with ambitious programmers who want to do more than what's possible today. I don't want to collaborate with programmers whose souls are already dead. > Can anyone help me with this? Is this documented anywhere? There's no documentation. I hope my attempts to explain seccomp, io_uring and Boost.Asio were useful to you. [1] https://security.googleblog.com/2023/06/learnings-from-kctf-vrps-42-linux.h… [2] https://stackoverflow.com/a/1151077/883113

1 0

[release] Boost 1.90.0 beta 1 released
by Marshall Clow 14 Nov '25

14 Nov '25

Boost release 1.90.0 beta 1 is now available at: https://archives.boost.io/beta/1.90.0.beta1/source/ The SHA256 checksums are: 8072831c2c54c7e0e99c69e934b5694574565dd435de19a0a43f7bf7dabad71b boost_1_90_0_b1.zip d1754f544e83418c2b5fe18245666830088948cb3629d2b346d56f31c71138e5 boost_1_90_0_b1.tar.bz2 c94235eb00edc732253d3ae8000a489ffc5773f34cd98bd7645d54cb4ae2482a boost_1_90_0_b1.7z 0f55a646eaed4daf110eeec7c2c70e2c7058efa77eef31137248a6e2cf1412da boost_1_90_0_b1.tar.gz Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- The release managers

3 3

Using lambda or functor as match_condition with boost::asio::read_until()
by Klebsch, Mario 28 Oct '25

28 Oct '25

Hello, I want to use boost::asio::read_until() and pass a functor as match condition. But I don't get it to compile. Here is my source code: #include <boost/asio.hpp> using namespace boost::asio; using iterator = buffers_iterator<streambuf::const_buffers_type>; struct completion_functor { std::pair<iterator, bool> operator()(iterator begin, iterator end) { return {}; } }; completion_functor functor; static_assert(is_match_condition<completion_functor>::value, "completion_functor must be match condition"); static_assert(is_match_condition<decltype(functor)>::value, "functor must be match condition"); std::pair<iterator, bool> completion_func(iterator begin, iterator end) { return functor(begin, end); } static_assert(is_match_condition<decltype(completion_func)>::value, "completion_func must be match condition"); auto lambda = [](iterator begin, iterator end) -> std::pair<iterator, bool> { return {}; }; static_assert(is_match_condition<decltype(lambda)>::value, "lambda must be match condition"); std::pair<iterator, bool> completion_func2(iterator begin, iterator end) { return lambda(begin, end); } static_assert(is_match_condition<decltype(completion_func2)>::value, "completion_func2 must be match condition"); int main(int argc, char *argv[]) { io_context ctx; ip::tcp::socket s{ctx}; streambuf buffer; read_until(s, buffer, '\n'); read_until(s, buffer, completion_func); read_until(s, buffer, completion_func2); // the following calls do not compile // read_until(s, buffer, functor); // read_until(s, buffer, lambda); } It seems, that boost::asio::is_match_condition<> does neither accept my lammda-function nor my functor. The only completion handler, that I get accepted, is a classic, free-standing function (and static class member functions, too). But in that function, calling the lambda or the functor does not seem to be a problem for the compiler. The documentation of read_until describes match_condition as "The function object to be called to determine whether a match exists." I would expect lambda functions and functors to be accepted as a function object. Do I have an error in the declaration of lambda or completion_functor::operator()? Does anybody now, how to get this working? I tried boost_1_73_0 and boost_1_88_0 with g++ (Gentoo 14.3.1_p20250801 p4) 14.3.1 20250801 and clang version 20.1.8 Thanks in advance, Klebsch Mario Funktion | R&D Tel: +49 (0) 531 38 701 718 Raum: Braunschweig, E20 Diese E-Mail und die an sie angehängten Dateien sind ausschließlich für Personen oder Institutionen bestimmt, deren Namen oben aufgeführt sind. Sie können Informationen enthalten, die durch das Berufsgeheimnis geschützt sind und deren Weitergabe strengstens untersagt ist. Jede elektronische Nachricht kann geändert werden. ACTIA lehnt jede Verantwortung für diese Nachricht ab. Der Inhalt dieser Nachricht stellt keine Verpflichtung seitens unseres Unternehmens dar. Wenn Sie kein Empfänger sind, weisen wir Sie darauf hin, dass das Lesen, Vervielfältigen oder Verteilen strengstens untersagt ist. Wir bitten Sie daher, uns umgehend über diesen Brief zu informieren und diese Nachricht sowie eventuell beigefügte Unterlagen aus Ihrem Postfach zu löschen. Danke. This e-mail and the files attached to it are intended exclusively for persons or institutions whose names are listed above. They may contain information that is protected by professional secrecy and the disclosure of which is strictly prohibited. Any electronic message can be modified. ACTIA declines all responsibility for this message. The content of this message does not represent a commitment on the part of our company. If you are not a recipient, we would like to point out that reading, copying or distribution is strictly prohibited. We therefore ask you to inform us immediately about this letter and to delete this message and any accompanying documents from your mailbox. Thank you.

3 2