March 2019 - Boost - lists.preview.boost.org

[release] 1.70 Windows binaries
by Sean Farrow 10 Mar '19

10 Mar '19

Hi, I know there is a discussion regarding building 1.70 with zlib in another thread, but wondered whether there are any binaries available for msvc without zlib for the 1.70 beta rc1/2? Kind regards Sean.

1 0

[variant2] documentation request
by Andrzej Krzemienski 10 Mar '19

10 Mar '19

Hi Peter, Given that the never-empty guarantee appears to be at the heart of the motivation for boost::variant2, I would suggest to: 1. put in the documentation some motivation behind pursuing the never-empty guarantee. 2. Make it clear that never-empty guarantee is not a strong exception-safety guarantee. 3. Describe the algorithm for achieving the guarantee. The current description does not seem to cover all interesting cases, and I found the behavior quite surprising. For instance, the variant's move assignment will sometimes use T's move assignment rather than move constructor when changing the variant's type, as in the following example: https://wandbox.org/permlink/GDRyS54bpdLP7GVa Regards, Andrzej

10 32

[gsoc19] Seeking Guidance along with mentor for Boost.GIL Project
by Keshav Gupta 10 Mar '19

10 Mar '19

Respected Sir, I am Keshav Gupta currently doing my B.E. in Computer Engineering from Thapar University, Patiala, Punjab, India. Actually I want to participate in GSOC19 and want to work with you during that period. Actually I am interested in implementing various Image Processing algorithms using BOOST.GIL. and I think that I can perfectly work upon this as I am also currently doing my research in the area of Fingerprint Matching and you absolutely know that this definitely includes the usage of image processing algorithms and that why I am interested for this as I know I have the proper knowledge of C++ along with image processing algorithms. Kindly guide me how to proceed further so as to increase my chances of getting being selected in GSOC19. Also please tell me any other way how to contact the mentor of this project as I have mailed him certain number of times but didn't get any response. Waiting for your reply Regards Keshav Gupta

2 1

Re: [boost] [Release] Boost 1.70.0 Beta 1 Release Candidate 2
by Peter Dimov 09 Mar '19

09 Mar '19

> Tom Kent wrote: > > > * Can't create libraries for bzip2 and zlib (showstopper? anyone else > > seeing this?) > > I haven't seen your initial report of this issue (on the users list?) but > it's probably caused by this change: > > https://github.com/boostorg/build/commit/5ad92cd76ff393792f30aa50688c95eff2… Or maybe not. This is in 1.69.0, so it can't be the cause.

1 0

[release] Boost 1.70.0 Beta 1 Release Candidate 1
by Marshall Clow 09 Mar '19

09 Mar '19

The release candidates for the first 1.70.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/ The release notes are not yet available. The SHA256 checksums are as follows: a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 ./boost_1_70_0_b1_rc1.7z 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 ./boost_1_70_0_b1_rc1.tar.bz2 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e ./boost_1_70_0_b1_rc1.tar.gz f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 ./boost_1_70_0_b1_rc1.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 Boost Release Managers

4 9

Interest in GSoC Project
by Kanav Gupta 09 Mar '19

09 Mar '19

Hello, I am third-year undergrad research student at International Institute of Information Technology, Hyderabad. I would like to contribute to Boost.GIL as a part of GSoC '19. I am currently working on a research project involving image processing and have also worked on various projects involving C++ so I guess I am competent for the project. Can you please guide me on how should I proceed? Thanks and Regards, Kanav Gupta

1 0

[release] 1.70.0 closed for major changes
by Marshall Clow 07 Mar '19

07 Mar '19

The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week. Also, if you're ready, you can also add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.q… > After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change. As always, the calendar for the release cycle is available at: https://www.boost.org/development/ Thanks, -- The Boost Release Team

7 9

[Release 1.70] Master branch is now closed for the beta
by Marshall Clow 07 Mar '19

07 Mar '19

Except with explicit permission by a release manager. Do whatever you want on develop, just don't change master. We'll re-open master after the beta. As always, check the calendar at https://www.boost.org/development 6-Mar: Boost 1.70.0 closed for all changes 13-Mar: Boost 1.70.0 beta; master branch re-opened 2-Aug: Release closed for all changes, except by permission of a release manager. 3-Apr: Boost 1.70.0 closed for all changes 10-Apr: Boost 1.70.0 release -- The release managers

2 1

[build] Boost.Build/develop broken with msvc?
by John Maddock 07 Mar '19

07 Mar '19

Currently I see: D:/data/boost/boost/tools/build/src/tools\msvc.jam:1388: in configure-really *** argument error * rule generate-setup-cmd ( version : command : parent : options * : cpu : global-setup ? : default-global-setup-options : default-setup ) * called with: ( 14.16.27023 14.11.25503 : D:/compilers/visual studio/2017/VC/Tools/MSVC/14.11.25503/bin/HostX64/x64 : D:\compilers\visual studio\2017\VC\Tools\MSVC\14.11.25503\bin\HostX64 : <command>D:\compilers\visual studio\2017\VC\Tools\MSVC\14.16.27023\bin\Hostx64\arm\cl.exe <command>D:/compilers/visual studio/2017/VC/Tools/MSVC/14.11.25503/bin/HostX64/x64/cl.exe : i386 : : x86 : vcvars32.bat ) * extra argument 14.11.25503 D:/data/boost/boost/tools/build/src/tools\msvc.jam:1003:see definition of rule 'generate-setup-cmd' being called D:/data/boost/boost/tools/build/src/tools\msvc.jam:393: in configure D:/data/boost/boost/tools/build/src/tools\msvc.jam:345: in msvc.init D:/data/boost/boost/tools/build/src/build\toolset.jam:44: in toolset.using D:/data/boost/boost/tools/build/src/build\project.jam:1104: in using C:\cygwin64\home\John Maddock\user-config.jam:46: in modules.load D:/data/boost/boost/tools/build/src\build-system.jam:255: in load-config D:/data/boost/boost/tools/build/src\build-system.jam:453: in load-configuration-files D:/data/boost/boost/tools/build/src\build-system.jam:607: in load D:\data\boost\boost\tools\build\src/kernel\modules.jam:295: in import D:\data\boost\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build D:\data\boost\boost\boost-build.jam:17: in module scope Master is fine BTW. Best, John. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 3

[interprocess] support for a new synchronisation mechanism
by Dudi Likvornik 06 Mar '19

06 Mar '19

Hi, My name is David, I would like to suggest a new synchronisation mechanism based on linux futex. as far as I saw, its not being supported as of now with in the interprocess communication library. One suggestion is to support a mutex, here is an example, possible partial implementation, based upon the following paper: http://dept-info.labri.fr/~denis/Enseignement/2008-IR/Articles/01-futex.pdf Mutex::Mutex(): m_word(UNLOCK) {} void Mutex::lock() { int lockState = UNLOCK; if(std::atomic_compare_exchange_strong(&m_word, &lockState, static_cast<int>(LOCK_SINGLE)) == false) { if(lockState != LOCK_MANY) lockState = std::atomic_exchange(&m_word, static_cast<int>(LOCK_MANY)); while(lockState != UNLOCK) { #if defined(__linux) syscall(SYS_futex, &m_word, FUTEX_WAIT, LOCK_MANY, nullptr, nullptr, 0); #else throw Exception(__CORE_SOURCE, "wait is not being supported by current platform"); #endif lockState = std::atomic_exchange(&m_word, static_cast<int>(LOCK_MANY)); } } } void Mutex::unlock() { if(std::atomic_fetch_sub(&m_word, 1) == LOCK_SINGLE) return; m_word = UNLOCK; #if defined(__linux) syscall(SYS_futex, &m_word, FUTEX_WAKE, 1, nullptr, nullptr, 0); #else throw Exception(__CORE_SOURCE, "wake is not being supported by current platform"); #endif } bool Mutex::try_lock() { int lockState = UNLOCK; return std::atomic_compare_exchange_strong(&m_word, &lockState, static_cast<int>(LOCK_SINGLE)); } ————————————————————————————————————————————————————————— And a conditional variable: Condition::Condition(): m_command(SLEEP), m_waitersCount(0){} void Condition::signal(Command command) { m_wakeLock.lock(); if(m_waitersCount == 0) { m_wakeLock.unlock(); return; } m_command.store(command, std::memory_order_relaxed); #if defined(__linux) syscall(SYS_futex, &m_command, FUTEX_WAKE, command == NOTIFY_ONE ? 1 : std::numeric_limits<int>::max(), nullptr, nullptr, 0); #else throw Exception(__CORE_SOURCE, "wake is not being supported by current platform"); #endif while(m_command.load(std::memory_order_relaxed) != SLEEP && m_waitersCount.load(std::memory_order_relaxed) != 0){} m_wakeLock.unlock(); } void Condition::wait(std::unique_lock<core::Mutex> &lock) { m_waitersCount++; lock.unlock(); while(true) { while(m_command.load(std::memory_order_relaxed) == SLEEP) #if defined(__linux) syscall(SYS_futex, &m_command, FUTEX_WAIT, SLEEP, nullptr, nullptr, 0); #else throw Exception(__CORE_SOURCE, "wait is not being supported by current platform"); #endif int fromCommand_one = NOTIFY_ONE; if(m_command.compare_exchange_strong(fromCommand_one, static_cast<int>(SLEEP), std::memory_order_relaxed)) { m_waitersCount--; lock.lock(); return; } else if(m_command.load(std::memory_order_relaxed) == NOTIFY_ALL) { if(m_waitersCount.fetch_sub(1, std::memory_order_relaxed) == 1) m_command.store(SLEEP, std::memory_order_relaxed); lock.lock(); return; } } } ConditionVariable::ConditionVariable() {} void ConditionVariable::wait(std::unique_lock<core::Mutex> &lock) { m_condition.wait(lock); } void ConditionVariable::notify_one() { m_condition.signal(Condition::NOTIFY_ONE); } void ConditionVariable::notify_all() { m_condition.signal(Condition::NOTIFY_ALL); } class ConditionVariable { public: ConditionVariable(); ConditionVariable(const ConditionVariable&) = delete; ConditionVariable& operator=(const ConditionVariable&) = delete; void wait(std::unique_lock<Mutex>& lock); template<typename Predict> void wait(std::unique_lock<Mutex>& lock, const Predict& predict) { while(predict() == false) m_condition.wait(lock); } void notify_one(); void notify_all(); private: Condition m_condition; }; Your thoughts of the idea, if any. p.s. Please be soft, its my first post ever :).

1 0