[release] Boost 1.80.0 Beta 1 Release Candidate 1 is available
Available at: https://boostorg.jfrog.io/ui/native/main/beta/1.80.0.beta1/source The SHA256 checksums are as follows: b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.bz2 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.7z ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.tar.gz 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d boost_1_80_0_b1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers
On Jul 7, 2022, at 11:16 AM, Marshall Clow
Available at: https://boostorg.jfrog.io/ui/native/main/beta/1.80.0.beta1/source
The SHA256 checksums are as follows:
b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.bz2 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.7z ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.tar.gz 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d boost_1_80_0_b1.zip
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Successfully built the libraries in Mac OS 10.15.7, with "Apple clang version 11.0.3 (clang-1103.0.32.62)” and C++ 03/11/14/17/2a. — Marshall
On Thu, Jul 7, 2022 at 1:16 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
Available at: https://boostorg.jfrog.io/ui/native/main/beta/1.80.0.beta1/source
The SHA256 checksums are as follows:
b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.bz2 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.7z ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.tar.gz 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d boost_1_80_0_b1.zip
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Looks good on Windows/Visual Studio. toolset arch compile Link Execute msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X msvc-14.2 32 X X X msvc-14.2 64 X X X msvc-14.3 32 X X X msvc-14.3 64 X X X Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. Full build logs can be found here: https://gist.github.com/teeks99/bd67227ee76470cc2666305418f2ba0c Tom
In file included from /usr/include/c++/12/string:40, from ./boost/assert/source_location.hpp:15, from ./boost/exception/exception.hpp:9, from ./boost/throw_exception.hpp:21, from libs/filesystem/src/directory.cpp:16: In static member function ‘static constexpr std::char_traits<char>::char_type* std::char_traits<char>::copy(char_type*, const char_type*, std::size_t)’, inlined from ‘static constexpr void std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::_S_copy(_CharT*, const _CharT*, size_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char> ]’ at /usr/include/c++/12/bits/basic_string.h:423:21, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Allocator>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::_M_replace(size_type, size_type, const _CharT*, size_type) [with _CharT = char; _T raits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /usr/include/c++/12/bits/basic_string.tcc:532:22, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Alloc>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::assign(const _CharT*) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /usr/include/c++/12/bits/basic_string.h:1647:19, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Alloc>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator=(const _CharT*) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /usr/include/c++/12/bits/basic_string.h:815:28, inlined from ‘boost::filesystem::path& boost::filesystem::path::assign(const value_type*)’ at ./boost/filesystem/path.hpp:349:22, inlined from ‘boost::system::error_code boost::filesystem::detail::{anonymous}::dir_itr_create(boost::intrusive_ptrboost::filesystem::detail::dir_itr_imp&, const boost::filesystem::path&, unsigned int, boost::files ystem::path&, boost::filesystem::file_status&, boost::filesystem::file_status&)’ at
Seems the build is a little noisy with warnings, using gcc-12 libs/filesystem/src/directory.cpp:446:26,
inlined from ‘void
boost::filesystem::detail::directory_iterator_construct(boost::filesystem::directory_iterator&, const boost::filesystem::path&, unsigned int, boost::system::error_code*)’ at libs/filesystem/src/dir
ectory.cpp:1066:51: /usr/include/c++/12/bits/char_traits.h:431:56: warning: ‘void* __builtin_memcpy(void*, const void*, long unsigned int)’ accessing 9223372036854775810 or more bytes at offsets -4611686018427387902 and [-461168601842738790 3, 4611686018427387904] may overlap up to 9223372036854775813 bytes at offset -3 [-Wrestrict] 431 | return static_cast
(__builtin_memcpy(__s1, __s2, __n));
Locale seems to also generate similar warnings. I'm not sure if this usage of memcpy is dubious or not. - Christian
On 7/12/22 19:05, Christian Mazakas via Boost wrote:
Seems the build is a little noisy with warnings, using gcc-12
In file included from /usr/include/c++/12/string:40, from ./boost/assert/source_location.hpp:15, from ./boost/exception/exception.hpp:9, from ./boost/throw_exception.hpp:21, from libs/filesystem/src/directory.cpp:16: In static member function ‘static constexpr std::char_traits<char>::char_type* std::char_traits<char>::copy(char_type*, const char_type*, std::size_t)’, inlined from ‘static constexpr void std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::_S_copy(_CharT*, const _CharT*, size_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char> ]’ at /usr/include/c++/12/bits/basic_string.h:423:21, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Allocator>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::_M_replace(size_type, size_type, const _CharT*, size_type) [with _CharT = char; _T raits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /usr/include/c++/12/bits/basic_string.tcc:532:22, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Alloc>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::assign(const _CharT*) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /usr/include/c++/12/bits/basic_string.h:1647:19, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Alloc>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator=(const _CharT*) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /usr/include/c++/12/bits/basic_string.h:815:28, inlined from ‘boost::filesystem::path& boost::filesystem::path::assign(const value_type*)’ at ./boost/filesystem/path.hpp:349:22, inlined from ‘boost::system::error_code boost::filesystem::detail::{anonymous}::dir_itr_create(boost::intrusive_ptrboost::filesystem::detail::dir_itr_imp&, const boost::filesystem::path&, unsigned int, boost::files ystem::path&, boost::filesystem::file_status&, boost::filesystem::file_status&)’ at libs/filesystem/src/directory.cpp:446:26,
It's coming from assigning a string literal to std::string, starting from here: https://github.com/boostorg/filesystem/blob/fcc11010a5899d6a16d3f0a9d60704f8... This is a bogus warning, please report it to gcc team.
This is a bogus warning, please report it to gcc team.
It seems like someone has beaten me to it! It looks like there's multiple ways of triggering this. This bug sounds exactly like what we're seeing so at least the gcc team is aware of the issue. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651 I suppose these warnings are not actionable on our end then. - Christian
Am 12.07.22 um 18:05 schrieb Christian Mazakas via Boost:
Locale seems to also generate similar warnings. I'm not sure if this usage of memcpy is dubious or not.
FWIW: I'm aware of those in Locale and have some workarounds in place which I hopefully am allowed to merge for the release. Alex
participants (5)
-
Alexander Grund
-
Andrey Semashev
-
Christian Mazakas
-
Marshall Clow
-
Tom Kent