- Boost - lists.boost.org

Merged #149, "Encode architecture and address model in versioned layout names"
by Peter Dimov 17 Oct '17

17 Oct '17

I've just merged https://github.com/boostorg/boost/pull/149, "Encode architecture and address model in versioned layout names", into the develop branch. Let's see how this goes. Welcome to 2005. :-)

6 10

How to build boost on windows with Clang/LLVM
by degski 17 Oct '17

17 Oct '17

With the latest snapshot builds of clang, thin LTO is supported on Windows. This thin LTO gives very interesting (speed) results. I would therefore like to start to build boost with clang and no longer with msvc. I have msvc 15.4 installed (the latest incarnation). I made a project-config.jam: =============start=============== import option ; using clang : 6.0 : clang++.exe : <cxxflags>-fmacro-backtrace-limit=0 <cxxflags>-Wno-invalid-token-paste <compileflags>-fmsc-version=1911 <linkflags>-fuse-ld=lld <linkflags>-flto=thin ; option.set keep-going : false ; ==============end=============== I call: bjam -a -d+2 cxxflags="-O0" "-sZLIB_SOURCE=%HOME%\zlib-1.2.8" "-sBZIP2_SOURCE=%HOME%\bzip2-1.0.6" variant=debug instruction-set=haswell threading=multi link=static runtime-link=static --prefix=%PREFIX% --build-dir=c:\boost-build address-model=64 architecture=x86 toolset=msvc --without-python --without-mpi --disable-filesystem2 install This does not work. What is the proper way to compile boost on windows using clang++.exe or clang-cl.exe for use with VS2017. degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798

3 7

Looking for a task to contribute to boost
by vivek pandya 17 Oct '17

17 Oct '17

Hello Boost Developers, I am Vivek. I contribute small patches to LLVM project. I wanted to work for boost open source project to enhance my C++ knowledge. Could someone suggest some project to me? I will be able to complete task suitable for Google Summer of Code with help and guidance form community. Please also suggest required assignments as I am not a frequent user of Boost libraries. Thanks, Vivek

3 2

Recommend dropping test coverage on msvc-7.1 and msvc-8.0
by James E. King, III 16 Oct '17

16 Oct '17

MSVC 7.1 and MSVC 8.0 are currently listed as "tested" in the Boost 1.65.1 release notes however there are a lot of projects that do not seem to support them well, if at all: http://www.boost.org/development/tests/master/developer/issues.html <http://www.boost.org/development/tests/develop/developer/issues.html> It looks like a large number of libraries will no longer build properly against them based on this report. I'm not sure what the procedure is to come to an agreement to drop a compiler in a release, but it looks like we should consider dropping msvc-7.1 and msvc-8.0. These are very old compilers for Windows development. Dropping them would also allow folks to more easily focus on failures in this report to make sure a release is as clean as possible and simplify the test matrix a little bit. Appveyor only supports back to Visual Studio 2010 at this point, so our ability to get pre-commit checks on compilers before msvc-10.0 is solely based on maintainer effort. I suspect this effort is no longer justified based on the age of the compilers. Thanks - Jim

13 31

Bjam broken on windows with VS2017?
by degski 16 Oct '17

16 Oct '17

My lappie has vs2017 installed, latest (15.4) version, from some days ago. I did the following: 1. Put a clean copy of the boost 1.65.1 source in c: root. 2. issue 'bootstrap.bat' in c:\boost_1_65_1\ (ordinary prompt, no vs thingy). This creates a project-config.jam msvc file. 3. Copied (overwrote project-config.jam) the below contents as project-config.jam to c:\boost_1_65_1\ =======start======= import option ; using clang : 6.0 : "C:\\Program Files\\LLVM\\bin\\clang++.exe" : <compileflags>-fmsc-version=1911 <compileflags>-DBOOST_USE_WINAPI_VERSION=0x1000 <compileflags>-DBOOST_USE_WINDOWS_H=1 <compileflags>-D_WIN32_WINNT=0x1000 <compileflags>-DNOMINMAX <ranlib>"C:\\Program Files\\LLVM\\bin\\llvm-ranlib.exe" <archiver>"C:\\Program Files\\LLVM\\bin\\llvm-ar.exe" <linkflags>-fuse-ld=lld <linkflags>-flto=thin ; option.set keep-going : false ; =======end======== 4. issue 'bjam -d0 --clean' The script of that, and the result is below: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Users\User>cd \ C:\>cd boost_1_65_1 C:\boost_1_65_1>bootstrap.bat Building Boost.Build engine Bootstrapping is done. To build, run: .\b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/build/doc/html/index.html C:\boost_1_65_1>bjam -d0 --clean 'C:/Program' is not recognized as an internal or external command, operable program or batch file. etc.. etc... the rest is history? Any ideas? degski

2 3

'Fibre safe optimisations' with gcc/clang (non Windows target) and Boost.Context
by james 15 Oct '17

15 Oct '17

I was considering whether I could/should build an actor system on Rust rather than C++, since it would be an interesting exercise for me. And then I found this article: https://www.reddit.com/r/rust/comments/56wgzq/status_of_coroutines/ In particular: > we noticed that the Rust stdlib is actually using TLS (!) to implement exceptions It seems to me that in practice other compilers might use some sort of thread-local hook for exceptions, whether it is TLS or something lower-level that supports TLS. And that the issue is whether the compiler will assume that the address of the TLS (or thread information block etc) is volatile, or can be cached in a stack frame or register across calls. It seems to me that any such caching of an address might cause difficulty, not just in Rust but also other languages. Microsoft's compiler explicitly has a switch for 'fibre safe optimisations' that disables such caching. The worry I have is code like this: void foo() { try { A() } catch (...) {} B(); // Can switch the context to another underlying OS thread try { C() } catch (...) {} } I am concerned that information about exception handling that was acquired for the first try block, might be retained in the frame and reused in the second try block. and the information might be captured in the frame and/or registers that get saved in the context, but in an arbitrary way. I suspect that access to explicit ABI TLS or C++ thread local is also impacted, although it might be easier to avoid. I guess its not a complete show-stopper if we ensure that fibres never migrate between OS threads, but that is somewhat inconvenient. So - is this actually a Rustc specific issue?

1 0

printf official specs or docs, ISO C99, and C++
by James E. King, III 14 Oct '17

14 Oct '17

I found https://svn.boost.org/trac10/ticket/10541 today and my guess is Boost.Format hasn't been updated to support the ISO C99 extensions, or the Microsoft type formats. Before any work is done on this, I'm looking for any official C++ documentation related to printf support requirements. For example the compatibility section in http://www.cplusplus.com/reference/cstdio/printf/ indicates certain language levels have requirements. Thanks, Jim

3 3

[build] Building library with vc++ 64-bit does not find vcvarsall.bat
by Edward Diener 13 Oct '17

13 Oct '17

If I build any library with any version vc++ 64-bit compiler, by using address-model=64, the vcvarsall.bat is looked for at, for example with msvc-14.0, C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/vcvarsall.bat and is not found. Naturally this leads to basic compilation failures. The path for vcvarsall.bat for msvc-14.0 is C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat instead. All versions of vc++ follow this path structure for vcvarsall.bat Building with any version of vc++ 32-bit, by not specifying the address-model, works correctly.

3 4

1.65.1 as modular packages on Conan.io
by Rene Rivera 13 Oct '17

13 Oct '17

Following on with the announcement before CppCon of the 1.64.0 modular packages here we are with more. I'm pleased to announce that the 1.65.1 Boost C++ Libraries are now available individually using the Conan package manager. There's even some improvements for the 1.64.0 package also :-) Find out more from the Bincrafters post here <http://bit.ly/2g6VEpp>[1]. For help using the packages you can bug the Bincrafters team in the #Conan CppLan Slack channel <http://bit.ly/2ykeqC0>[2]. Conan is a C/C++ (and more) package manager that supports an open ended set of build system and tool integrations including: VisualStudio, Xcode, CLion, Ninja, QMake, Premake, and yes even CMake <http://bit.ly/2xzhpbg>[3]. [1] <https://bincrafters.github.io/2017/10/13/Conan-Packages-Boost-1-65-1/> [2] <https://cpplang.now.sh/> [3] <http://docs.conan.io/en/latest/integrations.html> -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net

1 0

Maintainers: Adding Coverity Scan to your library
by James E. King, III 12 Oct '17

12 Oct '17

I have completed the work necessary to add Coverity Scan to Boost.Uuid and wanted to share the steps involved. This work can be carried into other libraries fairly easily. 1. Go to Coverity Scan: https://scan.coverity.com/ 2. Sign up/in with your Github account. 3. Create a project for your boostorg/library. It will take about 24 hours for them to activate your account so that you can use the results browser. To run a coverity scan manually: 1. Check out your project master (or whatever branch you want to scan). 2. cd into BOOST_ROOT (where "libs/" is located) 3. Run the libs/uuid/covscan.sh script with the following environment variables set: A. COVERITY_SCAN_TOKEN: the project token in coverity scan B. COVERITY_SCAN_NOTIFICATION_EMAIL: your email C. SELF: your library name, for example SELF=uuid for Boost.Uuid 4. You will need to clean up some cruft it leaves behind as the script is designed for Travis CI - just a couple directories starting with "cov" and a tar.xz file. To integrate coverity scans for every pull request or push into master with Travis CI: 1. Make sure you have Travis CI set up properly to build your project. 2. Copy the Coverity Scan stanza from libs/uuid/.travis.yml into your .travis.yml file. Note that the Boost.Uuid travis configuration now uses jobs instead of matrix, as jobs allow for conditions. I would encourage you to convert your .travis.yml to use jobs as well. 3. The next pull request into master, or the next push into master, will trigger a build, and any build for master will run covscan.sh and upload the data. You can add component regular expressions to ignore/omit other boost library errors if you wish. Here are the results for Boost.Uuid. I have not excluded other components yet: https://scan.coverity.com/projects/boostorg-uuid Initially I saw a flurry of "unhandled exception" items which I dismissed as intentional (i.e. I want the test to segfault if an unexpected exception is thrown so that I can debug it), and that will likely be a common practice for test files, but should not be for implementations. I also caution folks against marking something as a false positive. Approach it with the mindset of, "it must be a fault of the library" before jumping to, "it must be a fault in Coverity" and really convince yourself it is not a code issue. Even if you do not have travis integration in your library, running a manual scan will help you improve the quality of your library, so I recommend everyone at least do that much. - Jim

5 5