- Boost-users - lists.preview.boost.org

Jamshell query
by Mohammed Zahid 03 Sep '21

03 Sep '21

Hi, I am trying to run boost build in distributed environment by setting JAMSHELL I tried setting as environment variable and passing as command line variable -sJAMSHELL= Both didn't work https://github.com/bfgroup/b2/discussions/78 Need you guidence on how to do it. Thanks, Mohammed zahid

1 0

3D Tree Queries
by Glenn, Rachel M 02 Sep '21

02 Sep '21

I have a question about 3D RTree spatial queries, like a cube, sphere, or something. Are there any examples of how that can be done? I know how to do it for 2D RTree. Do you recommend the regular RTREE or a is there another one to use, like an rstar, that would be better? Thanks, Rachel

3 2

[Compute] automatically determine work group size
by Stephan Menzel 30 Aug '21

30 Aug '21

Hello everyone, I have recently made the switched an existing OpenCL application to boost compute. For reasons mostly. Now the transition went well for the most part but I struggle with one feature that appears to be missing. The determination of the local work group size. Originally the code was using clEnqueueNDRangeKernel() which has an option for the local work group size called local_work_size. When left empty, the system will determine that value itself at a small cost. Boost compute doesn't seem to have that. When I process an image for example: command_queue.enqueue_nd_range_kernel(kernel, bc::extents<2>{ 0, current_line }, bc::extents<2>{ width, height }, bc::extents<2>{ 128, 1 }); The last parameter is very hard for me to understand. I know roughly what it is and I understand it has to be dividable by 64, the total size (width * height) however has to be a multiple of it too, so there's a bunch of rules that apply and I would much rather leave that auto-determined as it was before. Leaving it bc::extents<2>{ 0, 0 } throws an assertion. So, essentially: Is there a way to leave it empty to be auto-defined? Cheers, Stephan

1 0

boost/rational.hpp and VS2019
by John Emmas 24 Aug '21

24 Aug '21

I'm guessing this might be solvable by updating to a newer version of boost (currently I'm running ver 1.71.0) but before updating, I wondered if there might be something obvious that 'm missing.... I'm building with Visual Studio 2019 and I get a whole bunch of errors simply by adding this line to an empty source file:- #include "boost/rational.hpp" It seems to be the same 6 errors but at various different lines - i.e. these errors, over & over again:- Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\ammintrin.h(146,19): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\ammintrin.h(146,8): error C2146: syntax error: missing ';' before identifier '_mm_macc_ps' Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\ammintrin.h(147,20): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\ammintrin.h(147,9): error C2146: syntax error: missing ';' before identifier '_mm_macc_pd' Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\ammintrin.h(148,19): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include\ammintrin.h(148,1): error C2086: 'int __m128': redefinition I just wondered if this might ring a bell with someone? e.g. might there be some preprocesser #define that I should've defined? (or a #define that I shouldn't be defining...) Thanks for any suggestions, John

3 18

Boost's Stage\Lib *.a Files
by Alexander Tanseco 23 Aug '21

23 Aug '21

I am running a tutorial program and I found out that in the program's build options under Linker settings/Link Libraries I can put both or either of the ff and the program compiles & runs without errors. What is the difference between the two? libboost_filesystem-mgw8-mt-d-x64-1_77.dll.a OR libboost_filesystem-mgw8-mt-x64-1_77.dll.a

2 1

[multiprecission] Large divides layered on 128 bit divides
by Neill Clift 21 Aug '21

21 Aug '21

Hi, The architecture of cpp_int being build on 64 bit arithmetic using 128 bit double_limb_type is interesting. I have a question on the large divide (divide_unsigned_helper). It uses the upper portions of the large integers to get an estimation of the quotient. Subtracts out a multiple of that quotient and repeats. It does this in 128 bit values if available from the compiler: double_limb_type a = (static_cast<double_limb_type>(prem[r_order]) << CppInt1::limb_bits) | prem[r_order - 1]; double_limb_type b = py[y_order]; double_limb_type v = a / b; The compiler emulates this operation in the routine __udivmodti4 which itself uses an iterative approach. It seems to use a pretty basic shift and subtract algorithm mind you. As a general rule for multiprecision is it OK to layer the Knuth like algorithm D on top of each other this way. I have no idea myself but wonder if this is a known issue. I would have guessed that it made sense to do a 64 by 64 bit divide to guess the quotient and repeat. Thoughts? Thanks. Neill.

2 2

[multiprecission] some thoughts on add_unsigned.hpp
by Neill Clift 19 Aug '21

19 Aug '21

Hi, In my program I see a lot of time taken up by add/subtract_unsigned. I have a couple of thoughts on the code: Carry propagation outside the range of the smallest number can be improved: for (; i < x && carry; ++i) carry = ::boost::multiprecision::detail::addcarry_limb(carry, pa[i], 0, pr + i); Maybe this: for (; i < x && carry; ++i) carry = ::boost::multiprecision::detail::addcarry_limb(0, pa[i], 1, pr + i); This generates just an inc on my machine but unfortunately it doesn't eliminate the loads and stores. I think on average the carry chain must be small though. You have the same situation on subtract. add_unsigned and subtract_unsigned are inconsistent at the tail end after carry propagation: add_unsigned: if (i == x && carry) { // We overflowed, need to add one more limb: result.resize(x + 1, x + 1); if (result.size() > x) result.limbs()[x] = static_cast<limb_type>(1u); } else std::copy(pa + i, pa + x, pr + i); <--- if I == x we do the copy. We also do the copy even if the output and input overlap subtract_unsigned: // Any remaining digits are the same as those in pa: if ((x != i) && (pa != pr)) <-------- we do these checks here and avoid the copy std_constexpr::copy(pa + i, pa + x, pr + i); I am seeing a lot of time being used by that general copy above in add_unsigned when it can be avoided. This stuff is totally awesome and works well in my program. So thanks for working on this stuff. Neill.

2 1

Boost Installation in Codeblocks
by Alexander Tanseco 18 Aug '21

18 Aug '21

To Gavin Lambert, many thanks for your help. I finally got my program running without errors with the ff settings: Global variable Lib: c:\boost_1_77_0\stage\lib Program's build options: Linker settings/Link libraries: blank Search Directories/Compiler: $(#boost) Search Directories/Linker: $(#boost.lib).

1 0

Boost uses unoptimized subtraction because of typo in intel_intrinsics.hpp
by Neill Clift 18 Aug '21

18 Aug '21

Hi, In my program I am seeing my code use the slower (I assume) subtract_unsigned_constexpr rather than subtract_unsigned with he borrow chain handled intrinsics. This seems to be happening because of these lines in intel_intrinsics.hpp: #if defined(__clang__) && (__clang__ < 9) // We appear to crash the compiler if we try to use these intrinsics? #undef BOOST_MP_HAS_IMMINTRIN_H #endif __clang__ is not the version but just the value 1. I expect this should be the major version instead: #define __clang__ 1 #define __clang_major__ 12 #define __clang_minor__ 0 As an aside 128bit support does work in windows with clang. I have to force it on like this: #define __STRICT_ANSI__ #define BOOST_HAS_INT128 #define BOOST_MP_HAS_IMMINTRIN_H #include <boost/multiprecision/cpp_int.hpp> Thanks. Neill.

2 1

boostrap fails with intel-linux
by Alain O' Miniussi 18 Aug '21

18 Aug '21

Hi I have a C++11 compiler: [alainm@zztop boost_1_77_0]$ icpc --version icpc (ICC) 2021.3.0 20210609 Copyright (C) 1985-2021 Intel Corporation. All rights reserved. [alainm@zztop boost_1_77_0]$ I can use it to build b2: [alainm@zztop boost_1_77_0]$ icpc --version icpc (ICC) 2021.3.0 20210609 Copyright (C) 1985-2021 Intel Corporation. All rights reserved. [alainm@zztop boost_1_77_0]$ ./tools/build/src/engine/build.sh --cxx=icpc ... ### Using 'cxx' toolset. >>> Why cxx ? ... icpc (ICC) 2021.3.0 20210609 Copyright (C) 1985-2021 Intel Corporation. All rights reserved. ..... > icpc -DNDEBUG builtins.cpp class.cpp command.cpp compile.cpp constants.cpp cwd.cpp debug.cpp debugger.cpp execcmd.cpp execnt.cpp execunix.cpp filesys.cpp filent.cpp fileunix.cpp frames.cpp function.cpp glob.cpp hash.cpp hcache.cpp hdrmacro.cpp headers.cpp jam_strings.cpp jam.cpp jamgram.cpp lists.cpp make.cpp make1.cpp md5.cpp mem.cpp modules.cpp native.cpp object.cpp option.cpp output.cpp parse.cpp pathnt.cpp pathsys.cpp pathunix.cpp regexp.cpp rules.cpp scan.cpp search.cpp startup.cpp subst.cpp sysinfo.cpp timestamp.cpp variable.cpp w32_getreg.cpp modules/order.cpp modules/path.cpp modules/property-set.cpp modules/regex.cpp modules/sequence.cpp modules/set.cpp -o b2 > cp b2 bjam [alainm@zztop boost_1_77_0]$ But bootstrap.sh fails to see it: alainm@zztop boost_1_77_0]$ ./bootstrap.sh --with-toolset=intel-linux Building B2 engine.. A C++11 capable compiler is required for building the B2 engine. Toolset 'intel-linux' does not appear to support C++11. ... ** Note, the C++11 capable compiler is _only_ required for building the B2 ** engine. The B2 build system allows for using any C++ level and any other ** supported language and resource in your projects. ... You can specify the toolset as the argument, i.e.: ./build.sh [options] gcc Toolsets supported by this script are: acc, clang, como, gcc, intel-darwin, intel-linux, kcc, kylix, mipspro, pathscale, pgi, qcc, sun, sunpro, tru64cxx, vacpp ## And then a lot of comment regarding build.sh which we did not called ourselve so not very usefull Failed to build B2 build engine [alainm@zztop boost_1_77_0]$ Any idea of what went wrong ? Thanks ---- Alain Miniussi DSI, Pôles Calcul et Genie Log. Observatoire de la Côte d'Azur Tél. : +33492003009 (Mont-Gros) +33483618544 (Sophia Antipolis) +33609650665

1 0