Re: [release] Boost 1.82.0 beta 1 released

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2023-03-27 12:24:33

On 3/15/23 18:38, Marshall Clow via Boost wrote:
> Boost release 1.82.0 beta 1 is now available at:
> 	https://boostorg.jfrog.io/artifactory/main/beta/1.82.0.beta1/source/
> 
> The SHA256 checksums are:
> efe17bea3f0b2c11f34828f37d5777f30eb6fef57af355c6a6664b08a4339999  boost_1_82_0_b1.7z
> 0af2a60f76abb4f411b1bd9c1a553f64454d9414990e8cc12f02f3b431e2ac45  boost_1_82_0_b1.tar.gz
> 495b2ae2f6970ea1e635f80222d9f6978148496cdd163e87c37cdd6de3b5ccfc  boost_1_82_0_b1.zip
> edf4cb9e8e5a14412b91311438478ef6ce12afe2a54714eb2f0632a454c3d8d5  boost_1_82_0_b1.tar.bz2
> 
> Release notes (still need updates):
> 	https://www.boost.org/users/history/version_1_82_0.html
> 
> Please try the beta and report any problems you encounter.

There is a bug in Boost.ASIO that prevents Boost.Log from compiling with
gcc 4.4 and clang 3.5. The bug is in BOOST_ASIO_ASSUME definition:

https://github.com/boostorg/asio/blob/boost-1.82.0.beta1/include/boost/asio/detail/config.hpp#L2119-L2130

1. gcc 4.4 does not support __builtin_unreachable, which makes the
__GNUC__ branch definition to fail.

2. clang 3.5 doesn't support __builtin_assume and uses the last fallback
option. There, BOOST_ASIO_ASSUME is defined without arguments, meaning
it expands to incorrect code like `(void)0(base != 0)`.

GitHub is dead for me ATM, so I can't create a PR.