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

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

Boost Unit Test: How to run only the enabled tests of a test suite?
by Maarten Anonymous 28 Dec '17

28 Dec '17

Hey, I'm looking for a way to only run the enabled unit tests of a tests suite. I have the following test suite: #define BOOST_TEST_MODULE decorator_predicate#include <boost/test/included/unit_test.hpp>namespace utf = boost::unit_test; BOOST_AUTO_TEST_SUITE(test_suite_1) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() BOOST_AUTO_TEST_SUITE(test_suite_2) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() Compilation and running: # Compile the test g++ predicate.cpp -o predicate # List all tests./predicate --list_content test_suite_1* bare_test* enabled_test* disabled_test test_suite_2* bare_test* enabled_test* disabled_test # Run the tests that are enabled by default./predicateRunning 4 test cases... *** No errors detected # Here, I would like to only run the enabled tests of test_suite_1.# Instead, all tests are run. Including the disabled../predicate -t test_suite_1Running 3 test cases... predicate.cpp(21): error: in "test_suite_1/disabled_test": check false has failed *** 1 failure is detected in the test module "decorator_predicate" How can I only run the enabled tests of tst_suite1? Only bare_test and enabled_test should be run. Thanks!

2 1

Weird compilation error when using boost::geometry
by 邓尧 16 Nov '17

16 Nov '17

Hi, I have implemented my own "point" as specified by the point concept http://www.boost.org/doc/libs/1_59_0/libs/geometry/doc/html/geometry/refere… When I use it along with boost::geometry::model::polygon/multi_polygon, GCC refuses to compile, tested on GCC 4.9/5.2. What's even more weird is that CLANG 3.6 would happy accept my code. BTW, the Point implementation is part of a large project, it difficult to replace it with boost::geometry::model::point. Here is my code: Point.hpp > #ifndef RAPTOR_POINT_HPP_INCLUDED_ > > #define RAPTOR_POINT_HPP_INCLUDED_ > > >> #include <boost/mpl/int.hpp> > > #include <boost/geometry/core/access.hpp> > > #include <boost/geometry/core/cs.hpp> > > #include <boost/geometry/core/coordinate_type.hpp> > > #include <boost/geometry/core/coordinate_system.hpp> > > #include <boost/geometry/core/coordinate_dimension.hpp> > > #include <boost/geometry/geometries/polygon.hpp> > > #include <boost/geometry/multi/geometries/multi_polygon.hpp> > > >> namespace raptor { > > >> template<typename T, int tDimension = 2> > > class Point { > > public: > > Point() = default; > > >> Point(T a, T b) { > > data[0] = a; > > data[1] = b; > > } > > >> Point(T a, T b, T c) { > > data[0] = a; > > data[1] = b; > > data[2] = c; > > } > > >> T& operator [] (long index) { > > return data[index]; > > } > > >> const T& operator [] (long index) const { > > return data[index]; > > } > > >> private: > > T data[tDimension]; > > }; > > >> using CubicPoint = Point<long, 3>; > > using PlanarPoint = Point<long>; > > using SphericalPoint = Point<double>; > > >> template<typename T> > > using Polygon = boost::geometry::model::polygon<T>; > > >> template<typename T> > > using PolySet = boost::geometry::model::multi_polygon<Polygon<T>>; > > >> } // namespace raptor > > >> namespace boost { namespace geometry { namespace traits { > > >> template<typename Type, std::size_t tDimension> > > struct tag<::raptor::Point<Type, tDimension>> { > > typedef point_tag type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_type<::raptor::Point<Type, tDimension>> { > > typedef Type type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_system<::raptor::Point<Type, tDimension>> { > > typedef boost::geometry::cs::cartesian type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct dimension<::raptor::Point<Type, tDimension>> > > : public boost::mpl::int_<tDimension> { > > // EMPTY > > }; > > >> template<typename Type, std::size_t tDimension, std::size_t tIndex> > > struct access<::raptor::Point<Type, tDimension>, tIndex> { > > static Type get(const ::raptor::Point<Type, tDimension>& p) { > > return p[tIndex]; > > } > > >> static void set(::raptor::Point<Type, tDimension>& p, > > const Type& value) { > > p[tIndex] = value; > > } > > }; > > >> }}} // namespace boost::geometry::traits > > >> #endif // RAPTOR_POINT_HPP_INCLUDED_ > > A real simple main.cpp: > #include "Point.hpp" > > >> int main() { > > raptor::Polygon<raptor::SphericalPoint> pl; > > raptor::PolySet<raptor::SphericalPoint> set; > > return sizeof(pl) + sizeof(set); > > } > > > GCC compilation error: g++ main.cpp -std=c++14 > In file included from /usr/include/boost/geometry/core/access.hpp:20:0, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::traits::point_type<raptor::Point<double> >': /usr/include/boost/geometry/core/point_type.hpp:66:17: required from > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:45:5: error: no matching > function for call to 'assertion_failed(mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>))' BOOST_MPL_ASSERT_MSG ^ /usr/include/boost/mpl/assert.hpp:82:5: note: candidate: template<bool C> > int mpl_::assertion_failed(typename mpl_::assert<C>::type) int assertion_failed( typename assert<C>::type ); ^ /usr/include/boost/mpl/assert.hpp:82:5: note: template argument > deduction/substitution failed: /usr/include/boost/geometry/core/point_type.hpp:45:5: note: cannot > convert > 'boost::geometry::traits::point_type<Geometry>::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE48::assert_arg<raptor::Point<double> > >()' (type 'mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>)') to type 'mpl_::assert<false>::type {aka > mpl_::assert<false>}' BOOST_MPL_ASSERT_MSG ^ In file included from > /usr/include/boost/geometry/core/coordinate_type.hpp:21:0, from /usr/include/boost/geometry/core/access.hpp:24, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >': /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:66:17: error: no type named > 'type' in 'struct boost::geometry::traits::point_type<raptor::Point<double> > >' >::type type; ^ In file included from > /usr/include/boost/geometry/geometries/polygon.hpp:26:0, from Point.hpp:10, from main.cpp:1: /usr/include/boost/geometry/geometries/concepts/point_concept.hpp: In > instantiation of 'class > boost::geometry::concept::Point<raptor::Point<double> >': /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:93:10: > error: 'value' is not a member of > 'boost::geometry::dimension<raptor::Point<double> >' enum { ccount = dimension<Geometry>::value }; ^ Where is the problem ? or it's a GCC bug ? Thanks

3 4

Re: [Boost-users] Many undefined references for libboost_filesystem
by mahmood n 01 Nov '17

01 Nov '17

I used another gcc version 4.5 (Ubuntu 11.04) and it works without any problem! I don’t know what is wrong with gcc-4.6. Though the problematic platform was Kubuntuu 12.04. I am know trying with Ubuntu 12.04 which uses gcc-4.6 to see if it is really a gcc problem or the platform! Sent from Mail for Windows 10 From: Alex Perry Sent: Wednesday, October 18, 2017 4:45 PM To: mahmood n Subject: RE: [Boost-users] Many undefined references for libboost_filesystem Actually one other thought (though you may well have solved this by now). Are you sure that the boost libraries you are attempting to link to are using the same abi? Ie how were they built. I only glanced at the github stuff you pointed too but I think I remember that the last commit was 5 years ago or some such – so probably wasn’t using C++11. I note you are using an old (54) version of boost whilst the current is (65) so about 5 years ago as well – but that probably supported being built with c++11.so you might need to rebuild them if they were using a different version of the C++ standard (or any abi breaking change such as 32 vs 64 bit, static runtime vs dynamically loaded etc). Under windows boost normally encodes the abi into the library name and you just automagically (using a msvc extension) link to the appropriate one. That is not the normal way on linux since gcc doesn’t have autolinking so you normally end up sticking them into a separate lib directory and swapping the -L path depending on which abi you want Again though please note this is not boost specific – is just standard C / C++ / Fortran or any obj/link based language issues with building dependencies – (and why most have swapped to using cmake rather than vanilla make to avoid the pain). A. From: Alex Perry Sent: 17 October 2017 16:14 To: 'mahmood n' <nt_mahmood(a)yahoo.com> Subject: RE: [Boost-users] Many undefined references for libboost_filesystem Dropped the rest of the boost list since I’m sure not many are interested! > I didn’t want to have another pain for “finding how the verbose variable is set in the Makefile”!!! Not hard that one… just add it to the command line when you call make make verbose=1 ….. > The libraries do exist, so why on earth it can not link :( > mahmood@vb:AES$ g++ -fPIC -L/home/mahmood/boost_1_54_0/stage/lib -lboost_filesystem -lboost_system -m64 -o /home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/release/AES obj/x86_64/release/aescuda.cpp.o obj/x86_64/release/aesCudaUtils.cpp.o obj/x86_64/release/aesHost.cu.o -L/usr/local/cuda/lib64 -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../lib -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../common/lib/linux -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../../shared//lib -lcudart -L/usr/local/cuda/lib64 -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../lib -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../common/lib/linux -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../../shared//lib -lcudart -lcutil_x86_64 -lshrutil_x86_64 …. Nope the computer is telling you they don’t exist on those paths as given – unfortunately the computer is more likely to be correct than you on this! You have a lot of library paths being set there – possibly you have multiple versions of boost libraries so its finding the wrong one first so you have a version conflict Possibly the simplest way is create a noddy test and play with the command line till you work out what the problem is http://rextester.com/live/JDVHT54458 That will give you similar compile errors without -lboost_filesystem -lboost_system added to the compile line. Obviously that is using clang rather than gcc which you are using but the syntax and principles are pretty much the same between any c++ compiler HTH A.

5 6

Boost graph library algorithms - is it possible to use previous solutions to "warm start" a new related problem
by F1E2D3 F1E2D3 29 Oct '17

29 Oct '17

Hello, I am primarily an Operations Researcher, and prior to boost, was writing my own C++ code for specific network flow problems. I am now hoping to transition to boost::graph completely for my network flow problem solution needs. However, I have one major concern. In linear programming (I use CPLEX https://www.ibm.com/us-en/marketplace/ibm-ilog-cplex as my primary linear programming (LP) solver), once a problem is solved, say a Dijkstra's shortest path problem, the solver maintains the optimal basis. Then, if some problem parameter changes, the linear program need not be solved from scratch, but the current basis is first tested for optimality for the new problem as well. An example of this would be an increase in the cost of an arc that does not feature on the optimal path from source to destination in a shortest path problem. This increase in cost does not change the optimal path, and hence, it would be wasteful to solve this problem again from scratch. Does boost::graph have this capability that LP solvers have? I posted this question first on stack overflow and am posting it here now. The question was not completely answered there. A working code and small example are provided there. I am giving the link below. https://stackoverflow.com/questions/46986312/are-boostgraph-algorithms-capa… Any help will be appreciated. Thanks.

1 0

[review][DoubleEnded] Review Results
by Thorsten Ottosen 27 Oct '17

27 Oct '17

Dear users and members of Boost, I'm happy to to announce that Benedek Thaler's Boost.DoubleEnded is /conditionally/ accepted into Boost provided that it can be integrated smoothly with Boost.Container. There are several other conditions, some major and some minor which I will outline below. For now, I would like to thank everyone that participated with reviews and comments. We didn't have that many reviews, but the reviewers did spend a lot of time both on review and the following discussions. Special thanks also goes to Benedek for his hard work. It is not too often that a GSOC code ends with something of this quality. Two of the world's expert C++ container developers used phrases like "solid" and "everything looks clean and beautiful" about the implementation, "tests look very good, corner cases and all", "The reference section is very good". Congratulations, Benedek. ============== A path forward ============== Ion has most kindly accepted the idea of merging the library into Boost.Container. This consists of A. taking selected elements from batch_deque and adding them to boost::container::deque. B. putting devector into boost.container after changes have been applied to code and documentation C. back-porting the devector code to C++03 (C) does not need to happen immediately, that is, we can have a release where devector is available in a C++11 version. Ion has also most kindly agreed to help with this process. I will help write a new introduction that focuses on the main principles of devector. We also have a number of benchmarks which we can gather and use for a small section of on that topic. I'll leave it to you and Ion to work out the details. ========================== Detailed comments devector ========================== Apart from the merging with Boost.Container, the most heard complaint was about the "fat", the non-essential parts if the interface, that could be removed. This includes -- Remove the direct support for small buffer optimization form devector. When the time comes, provide small_devector similar to the way we have vector/small_vector (there is no requirement that small_devector is provided). -- remove all of the following: - all constructors that uses reserve_only_tag, - all constructors that uses unsafe_uninitialized_tag, - void unsafe_uninitialized_resize_front(size_type); - void unsafe_uninitialized_resize_back(size_type); - unsafe_push_front(...); - unsafe_push_back(...); -- add instead - constructors that uses default_init_t like boost.container - resize versions that uses default_init_t - T& unchecked_emplace_back(...) noexcept(...) - T& unchecked_emplace_front(...) noexcept(...) At some point, I hope we can upgrade default_init_t to mean no construction for all trivially copyable types. There was a wish for more symmetry in devector and so functions that break symmetry or can appear ambiguous should be removed. This means we should remove: -- capacity() There is no need for front_capacity() and back_capacity(). We could remove reserve(), but then we can't use devector with a flat_set. Reserve() should not be an alias for reserve_back() though, but controlled by the policy. We could remove resize(), but even deque has it where it means resize_back(). I totally agree it would be ideal to remove all of reserve(),resize(),capacity(),clear(), but I see no easy way we can use devector with flat containers if we remove the first and the last. Unless we start deprecating stuff in boost::deque/boost::vector and provide new consistent alternatives, we will never get a 100% satisfactory solution. At the end of the day, we need to be pragmatic, so if deprecation is not on the table, this seems the best we can do. Since we don't want two allocations implied by calling reserve_back() and reserve_front(), you can add a mechanism for doing that. That is, you can provide -- reserve( new_capacity ); -- reserve_front( new_front_capacity ) -- reserve_back( new_back_capacity ) -- reserve( new_front_capacity, new_back_capacity ) or, since reserve() is such a weird beast, simply provide -- reserve( new_capacity ); // for flat containers -- anticipate_front( new_front_elements ) -- anticipate_back( new_back_elements ) -- anticipate( new_front_elements, new_back_elements ) to get rid of the funky -- container.reserve_front( container.size() + new_front_elements ) dance. There were suggestions for shrink_back/front_to_fit, but since we are trying to remove fat, I suggest that we wait for a use-case. There were also suggestions that clear() should be amended. As the growth (or resizing policy) mandates what clear does, we need a way to escape. The minimal change that allows that is to provide -- clear( front_free_capacity ) which gives full power to the user. You may provide clear_back() as clear(0) and clear_front() as clear(c.size()+c.front_free_capacity()+c.back_free_capacity()). Ideally, clear() would have been removed entirely like capacity()/resize(), but like reserve(), it just seems like impossible when we start using it with flat containers. Other minor comments: - drop strong exception safety guarantees and do it like boost.container - prefer to make iterator a type (should be easy with reuse from boost::container::vector - allocator should not be inherted from - make clear O(1) amortized gurantees depend on growth policy - consider calling growth policy for resizing policy - make sure SFINAE works properly with constructors - make the default growth factor 2 (as we heard from Sean Parent: no factor below 2 is empirically good) - consider renaming front_free_capacity to free_front_capacity. Rationale: "front_capacity" is a concept, noun, and "free" is the adjective. Ditto for back_free_capacity. - remove size_type from growth policy and take it from the allocator - make the allocator template argument the 2nd argument - fix remaning TODO in code - documentation should not sell devector as drop-in replacement for vector, but rather stress it is not - the allocator supports needs to be improved. I guess doing it the Boost.Container way ensures that (ask Daniel James for help) - exception-safety issues pointed out by Ion - postconditions of insert/erase needs to specify behavior to front_free_capacity/back_free_capcity - use of local containers should be avoided - rotate should be avoided - delegate range move operations to those defined in Boost.Container - make sure all functions excepting non-overlapping range uses memcpy (not just memmove). This includes: - range constructor - copy-constructor - copy-assignment - range-assignment - range insert - destructor should used std::has_trivial_destructor to avoid loop in that case to make sure all compilers optimize it away (similar for erase). There is one final puzzle and that is the growth policy. I hope we can finalize that by testing Joaquin's and Ion's suggestions over the coming weeks. ============================= Detailed comments batch_deque ============================= For deque, the comments were similar, although there was far less to discuss than for devector. All agreed that one should be able to control the segment size. - stable_insert was not needed. - segment iteration was good, but should be usable with range-based for loop. The segment iterator should return a segment type if possible, and the segment should have begin(),end(),size() members. - since boost::deque already has a resize with default_init_t, that should be sufficient to provide fast serialization load for trivial types. No need for - resize_front - resize_back - unsafe_uninitialized_resize_front - unsafe_uninitialized_resize_back - reserve - shrink_to_fit() - capacity() The following are still needed for optimal code (or code that can be known not to reallocate, or for better locality in deserialization, avoiding double initialization) - free_front_capacity; - free_back_capacity; - reserve_front - reserve_back - unchecked_emplace_front - unchecked_emplace_back Boost.Container's unit-tests should be extended with those from batch_deque where it makes sense. Since segmented iteration was somewhat faster, it should be use internally where it makes sense. In particular - copy-constructor - copy-assignment - destructor As for devector, all constructor/functions that iterate over non-overlapping ranges should use memcpy. destructor should use is_trivially_destructible to ensure it is optimized away (similar for erase). ====================== Serialization comments ====================== I suggest that the default versions just do what Boost.Serialization does, perhaps just replacing resize with resize with default_init_t. That ensures it works correctly for all archive types. It also needs to use make_nvp() so the output is identical to std::vector. We will then talk to Robert about how we can take advantage of the binary archive in a correct fashion. ====================== kind regards Thorsten, review manager

3 3

[Container] Does deque allocate memory in default constructor?
by dariomt＠gmail.com 25 Oct '17

25 Oct '17

It seems std::deque implementations are allowed to allocate in the default constructor [1] However, boost::container::deque I think does not allocate in the default constructor, but the docs are not explicit about it. I can see in the docs: *Throws*: If allocator_type's default constructor throws. Which would mean that it cannot throw due to memory exhaustion, so it cannot allocate memory. Is my reasoning right? If yes, would it be possible to make this explicit in the docs? I think it is relevant, because it might be the deciding factor for switching from std::deque to boost::container::deque (as it might be my case). Thanks! [1] https://stackoverflow.com/questions/40203494/why-does-stddeque-allocate-mem…

2 1

Fwd: Boost compilation problems
by Berkus Karchebnyy 24 Oct '17

24 Oct '17

Hello, in attempt to build boost for android with more or less reasonable strict settings (-Werror) I uncovered some bugs which I cannot report on github because these projects have Issues disabled. I will post them here in hopes they will eventually reach appropriate maintainers. == ONE: boost.containers == clang-darwin.compile.c android-build/boost/bin.v2/ libs/container/build/clang-darwin-5.0~x86/debug/address- model-32/link-static/target-os-android/threading-multi/alloc_lib.o In file included from libs/container/src/alloc_lib.c:19: libs/container/src/dlmalloc_ext_2_8_6.c:1097:8: error: variable 'ret' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes- uninitialized] if (!PREACTION(m)) { ^~~~~~~~~~~~~ libs/container/src/dlmalloc_ext_2_8_6.c:1125:11: note: uninitialized use occurs here return ret; ^~~ libs/container/src/dlmalloc_ext_2_8_6.c:1097:4: note: remove the 'if' if its condition is always true if (!PREACTION(m)) { ^~~~~~~~~~~~~~~~~~~ libs/container/src/dlmalloc_ext_2_8_6.c:1095:4: note: variable 'ret' is declared here boost_cont_malloc_stats_t ret; ^ 1 error generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTAINER_STATIC_LINK=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/ libs/container/build/clang-darwin-5.0~x86/debug/address- model-32/link-static/target-os-android/threading-multi/alloc_lib.o" "libs/container/src/alloc_lib.c" == TWO: boost.serialization and monty python == (cue Benny Hill music) clang-darwin.compile.c++ android-build/boost/bin.v2/ libs/serialization/build/clang-darwin-5.0~x86/debug/ address-model-32/link-static/target-os-android/threading- multi/polymorphic_iarchive.o In file included from libs/serialization/src/polymorphic_iarchive.cpp:20: In file included from ./boost/archive/polymorphic_iarchive.hpp:32: ./boost/archive/detail/iserializer.hpp:69:7: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined] #if ! DONT_USE_HAS_NEW_OPERATOR ^ ./boost/archive/detail/iserializer.hpp:63:12: note: expanded from macro 'DONT_USE_HAS_NEW_OPERATOR' || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590) \ ^ ./boost/archive/detail/iserializer.hpp:212:9: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined] #if DONT_USE_HAS_NEW_OPERATOR ^ ./boost/archive/detail/iserializer.hpp:63:12: note: expanded from macro 'DONT_USE_HAS_NEW_OPERATOR' || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590) \ ^ 2 errors generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c++ -ftemplate-depth-255 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++14 -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/libs/serialization/build/ clang-darwin-5.0~x86/debug/address-model-32/link-static/ target-os-android/threading-multi/polymorphic_iarchive.o" "libs/serialization/src/polymorphic_iarchive.cpp" == THREE: boost.program_options == clang-darwin.compile.c++ android-build/boost/bin.v2/ libs/program_options/build/clang-darwin-5.0~x86/debug/ address-model-32/link-stati c/target-os-android/threading-multi/cmdline.o libs/program_options/src/cmdline.cpp:104:41: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror ,-Wshadow] cmdline::init(const vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:508:48: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror ,-Wshadow] cmdline::parse_long_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:545:49: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_short_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:611:47: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_dos_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:632:58: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_disguised_long_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:663:47: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_terminator(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:683:55: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::handle_additional_parser(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ 7 errors generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c++ -std=c++14 -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/libs/program_options/build/ clang-darwin-5.0~x86/debug/address-model-32/link-static/ target-os-android/threading-multi/cmdline.o" "libs/program_options/src/ cmdline.cpp" The entire set of compile flags and NDK version can be seen in the provided snippets. Thanks. -- Sr. Software Engineer [image: twilio] <http://www.twilio.com/?utm_source=email_signature> EMAIL berkus(a)twilio.com

1 0

Help needed in learning to use Boost.Asio
by Osman Zakir 24 Oct '17

24 Oct '17

I want to learn how to use Boost.Asio so I can then create an abstraction layer over it for HTTP and create a server and client. I need it for a web app I want to make. I know C++ isn’t a good choice for this sort of thing, but it’s still growing and getting better, so I wonder if there’s really no hope for it becoming a better choice for web development. Especially if someone were to propose a networking library for boost that also provides support for the HTTP protocol and maybe also RESTful services out of the box. Libraries in Boost have a high chance of making it into the standard, after all, so this could be a good idea. I’ve heard from many people that C++ is a waste of time, especially if one wants to get into web development and make a lot of money. Most people who want to web development are abandoning C++ in favor of languages Python that provide better support for web development. I don’t like this and I hope that C++ will also become better for the job soon so that it can pull back programmers that have left it for other languages. That’s also the reason why I want to use C++ here. I’m hoping that the Networking TS would be standardized and that the standardizing committee would also do something to make C++ overall better for the web, preferably as good as Python if possible. The difficulty of getting into and using C++ is also overly-exaggerated but it seems to be more because of C++ programmers not making their code simple and beautiful enough, so it’s also the language users’ fault. I want to try to change the negative views that people have of C++, as well. By the way, would it be a good idea to send an email asking about the future of C++, especially for web development, to Dr. Stroustrup if I can find a way to contact him? I know he’s a busy man and I’m also reluctant to this, but since he’s also on the standard-making committee, if he finds some free time to reply to my email, he should be able to tell me what to expect about C++ and its future. I’m sorry if this email got too long, though. Best regards. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

5 7

boost asio
by Sharma, Nishant 23 Oct '17

23 Oct '17

Hi, I have created an Asynchronous TCP server and client and it works fine. Since it is asynchronous, it uses API's like async_read, async_write etc.. Is it possible that the same code be used to do "synchronous" communication which results in blocking any further task in the queue unless the current i/o task is complete ? I have attached the example hereby. It has two folder for server and client.. First the server needs to be run and then the client. Best Regards, Nishant Sharma

3 5

boost fileystem issue
by Olivier Tristan 20 Oct '17

20 Oct '17

Hi Guys, I would like to bump this particular issue that is quite annoying for me. Basically it crashes as soon as you call boost::filesystem::exists in the ctor of a static variable initialized at program startup https://svn.boost.org/trac10/ticket/12987 Looks like there was a fix 4 month ago but this hasn't been pushed into the trunk yet Any idea how to push the process forward ? Thanks ! -- Olivier Tristan Research & Development www.uvi.net

2 2

Reconnecting a SSL socket correctly
by David Demelier 18 Oct '17

18 Oct '17

Hello, I'm trying to reconnect a SSL socket (using ssl::stream with tcp::socket) that has been closed only remotely. It looks like a shutdown on my client causes "stream truncated" error so I have no idea how can I connect my client socket again. I was thinking of just creating a new instance but the stream class is not copyable. Do you have any recommandations? Regards, -- David

2 1

[asio] null reference in epoll_reactor
by Phil Sean 18 Oct '17

18 Oct '17

Hi, Running the tutorial async TCP server (http://www.boost.org/doc/libs/1_65_1/doc/html/boost_asio/tutorial/tutdaytim…) or any other asynchronous operation in valgrind yields an error like this: = Syscall param epoll_pwait(sigmask) points to unaddressable byte(s) = epoll_pwait (in /usr/lib/libc-2.26.so) = boost::asio::detail::epoll_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) (in /.../server) = boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) (in /.../server) = boost::asio::detail::task_io_service::run(boost::system::error_code&) (in /.../server) = boost::asio::io_service::run() (in /.../server) = main (in /.../server) = Address 0x0 is not stack'd, malloc'd or (recently) free'd I suspect it's due to some recent changes because it didn't use to be an error. Boost version is 1.65.1(Arch Linux). Thank you.

2 2

git clone of boost
by Tim Burgess 18 Oct '17

18 Oct '17

Hi, Just been trying to find the address to clone boost, but was unsuccessful. Can anybody help me out please? Best wishes. Tim Burgess

2 1

Re: [Boost-users] Many undefined references for libboost_filesystem
by Mahmood N 17 Oct '17

17 Oct '17

Hi Daniel, I tried some other versions based on the release date of the project and boosts. I tried 1.38 and 40 and 42 and 44 and 46. All of them return some undefined references. How can i find which boost version is used in the project? Regards, Mahmood -------------------------------------------- On Sat, 10/14/17, Daniel Anderson <wonixen(a)gmail.com> wrote: Subject: Re: [Boost-users] Many undefined references for libboost_filesystem To: boost-users(a)lists.boost.org Cc: "Mahmood N" <nt_mahmood(a)yahoo.com> Date: Saturday, October 14, 2017, 12:53 AM you are probably using the wrong version of filesystem, or maybe of boost. often those projects need a specific boost version. 2017-10-13 14:24 GMT-04:00 Mahmood N via Boost-users <boost-users(a)lists.boost.org>: > Hi, > > I am trying to build a suite as described at > https://github.com/gpgpu-sim/ispass2009-benchmarks > > Some of the benchmarks use boost. For example, AES/Makefile has > > > > LINKFLAGS := -L$(BOOST_LIB) -lboost_filesystem > > > > Also, the Makefile.ispass-2009 in the root folder has the following settings > > > > SETENV=export BINDIR=$(BINDIR); \ > > export ROOTDIR=$(NVIDIA_COMPUTE_SDK_LOCATION)/C/src/; \ > > export BINSUBDIR=$(BINSUBDIR); \ > > export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; \ > > export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; \ > > export BOOST_VER=""; \ > > export OPENMPI_BINDIR=/usr/bin/; > > > > > > I manually built boost_1_46_0 with the steps described at > http://www.boost.org/doc/libs/1_46_1/doc/html/bbv2/installation.html > > The installations was successful and I can see lib/ and include/ folders > > > > mahmood@vb:boost_1_46_0$ find lib -name libboost_system* > > lib/libboost_system.so.1.46.0 > > lib/libboost_system.so > > lib/libboost_system.a > > mahmood@vb:boost_1_46_0$ find lib -name libboost_filesystem* > > lib/libboost_filesystem.so > > lib/libboost_filesystem.a > > lib/libboost_filesystem.so.1.46.0 > > > > > > > > However, as I run “make -f Makefile.ispass-2009”, I get many undefined > errors about libboost_filesystem. Please see below > > > > > > > > export > BINDIR=/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/; > export ROOTDIR=/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src/; export > BINSUBDIR=release; export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; export > BOOST_ROOT=/home/mahmood/boost_1_46_0/include; export BOOST_VER=""; export > OPENMPI_BINDIR=/usr/bin/; make noinline=0 -C AES > > make[1]: Entering directory > `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `readFromFileForm(boost::filesystem3::path&, std::vector<unsigned int, > std::allocator<unsigned int> >&)': > > aesCudaUtils.cpp:(.text+0x97d): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `readFromFileNotForm(boost::filesystem3::path&, char*, unsigned int)': > > aesCudaUtils.cpp:(.text+0xe81): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `getFileSize(boost::filesystem3::path&)': > > aesCudaUtils.cpp:(.text+0x1244): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > aesCudaUtils.cpp:(.text+0x1257): undefined reference to > `boost::filesystem3::detail::file_size(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `initAesCuda(std::basic_string<char, std::char_traits<char>, > std::allocator<char> >, unsigned char*, unsigned int, > std::basic_string<char, std::char_traits<char>, std::allocator<char> >, > char*, unsigned int)': > > aesCudaUtils.cpp:(.text+0x1c54): undefined reference to > `boost::filesystem3::path::wchar_t_codecvt_facet()' > > aesCudaUtils.cpp:(.text+0x1cab): undefined reference to > `boost::filesystem3::path::wchar_t_codecvt_facet()' > > aesCudaUtils.cpp:(.text+0x1ce5): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > aesCudaUtils.cpp:(.text+0x1d02): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `_GLOBAL__sub_I_aesCudaUtils.cpp': > > aesCudaUtils.cpp:(.text.startup+0x2b): undefined reference to > `boost::system::generic_category()' > > aesCudaUtils.cpp:(.text.startup+0x37): undefined reference to > `boost::system::generic_category()' > > aesCudaUtils.cpp:(.text.startup+0x43): undefined reference to > `boost::system::system_category()' > > obj/x86_64/release/aescuda.cpp.o: In function `_GLOBAL__sub_I_aescuda.cpp': > > aescuda.cpp:(.text.startup+0x68b): undefined reference to > `boost::system::generic_category()' > > aescuda.cpp:(.text.startup+0x697): undefined reference to > `boost::system::generic_category()' > > aescuda.cpp:(.text.startup+0x6a3): undefined reference to > `boost::system::system_category()' > > collect2: ld returned 1 exit status > > make[1]: *** > [/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin//release/AES] > Error 1 > > make[1]: Leaving directory > `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' > > make: *** [default] Error 2 > > > > > > > > Any thought on that? > > > Regards, > Mahmood > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users -- Daniel L'action accède à la perfection quand, bien que vivant, vous êtes déjà mort Bunan

6 14

Many undefined references for libboost_filesystem
by Mahmood N 13 Oct '17

13 Oct '17

Hi, I am trying to build a suite as described at https://github.com/gpgpu-sim/ispass2009-benchmarks Some of the benchmarks use boost. For example, AES/Makefile has LINKFLAGS := -L$(BOOST_LIB) -lboost_filesystem Also, the Makefile.ispass-2009 in the root folder has the following settings SETENV=export BINDIR=$(BINDIR); \ export ROOTDIR=$(NVIDIA_COMPUTE_SDK_LOCATION)/C/src/; \ export BINSUBDIR=$(BINSUBDIR); \ export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; \ export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; \ export BOOST_VER=""; \ export OPENMPI_BINDIR=/usr/bin/; I manually built boost_1_46_0 with the steps described at http://www.boost.org/doc/libs/1_46_1/doc/html/bbv2/installation.html The installations was successful and I can see lib/ and include/ folders mahmood@vb:boost_1_46_0$ find lib -name libboost_system* lib/libboost_system.so.1.46.0 lib/libboost_system.so lib/libboost_system.a mahmood@vb:boost_1_46_0$ find lib -name libboost_filesystem* lib/libboost_filesystem.so lib/libboost_filesystem.a lib/libboost_filesystem.so.1.46.0 However, as I run “make -f Makefile.ispass-2009”, I get many undefined errors about libboost_filesystem. Please see below export BINDIR=/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/; export ROOTDIR=/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src/; export BINSUBDIR=release; export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; export BOOST_VER=""; export OPENMPI_BINDIR=/usr/bin/; make noinline=0 -C AES make[1]: Entering directory `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' obj/x86_64/release/aesCudaUtils.cpp.o: In function `readFromFileForm(boost::filesystem3::path&, std::vector<unsigned int, std::allocator<unsigned int> >&)': aesCudaUtils.cpp:(.text+0x97d): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `readFromFileNotForm(boost::filesystem3::path&, char*, unsigned int)': aesCudaUtils.cpp:(.text+0xe81): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `getFileSize(boost::filesystem3::path&)': aesCudaUtils.cpp:(.text+0x1244): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' aesCudaUtils.cpp:(.text+0x1257): undefined reference to `boost::filesystem3::detail::file_size(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `initAesCuda(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, unsigned char*, unsigned int, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, char*, unsigned int)': aesCudaUtils.cpp:(.text+0x1c54): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' aesCudaUtils.cpp:(.text+0x1cab): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' aesCudaUtils.cpp:(.text+0x1ce5): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' aesCudaUtils.cpp:(.text+0x1d02): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `_GLOBAL__sub_I_aesCudaUtils.cpp': aesCudaUtils.cpp:(.text.startup+0x2b): undefined reference to `boost::system::generic_category()' aesCudaUtils.cpp:(.text.startup+0x37): undefined reference to `boost::system::generic_category()' aesCudaUtils.cpp:(.text.startup+0x43): undefined reference to `boost::system::system_category()' obj/x86_64/release/aescuda.cpp.o: In function `_GLOBAL__sub_I_aescuda.cpp': aescuda.cpp:(.text.startup+0x68b): undefined reference to `boost::system::generic_category()' aescuda.cpp:(.text.startup+0x697): undefined reference to `boost::system::generic_category()' aescuda.cpp:(.text.startup+0x6a3): undefined reference to `boost::system::system_category()' collect2: ld returned 1 exit status make[1]: *** [/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin//release/AES] Error 1 make[1]: Leaving directory `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' make: *** [default] Error 2 Any thought on that? Regards, Mahmood

2 1

[coroutine] MinGW: terminate called after throwing an instance of 'boost::context::detail::forced_unwind'
by Jan Niklas Hasse 13 Oct '17

13 Oct '17

Hi :) I've tried to compile this simple Boost.Coroutine example: #include <iostream> #include <boost/coroutine2/all.hpp> void foo(boost::coroutines2::asymmetric_coroutine<void>::push_type& yield) { for (int i = 0; i < 10; ++i) { std::cout << i << std::endl; yield(); } } int main() { boost::coroutines2::asymmetric_coroutine<void>::pull_type coroutine(foo); for (int i = 0; i < 5; ++i) { coroutine(); } } On Linux this works as expected, just as on Windows with Visual Studio. But when I cross-compile on Linux using i686-w64-mingw32-g++ src/main.cpp -lboost_context-mt The resulting exe crashes with: 0 1 2 3 4 5 6 terminate called after throwing an instance of 'boost::context::detail::forced_unwind' abnormal program termination There's a similar problem on StackOverflow: https://stackoverflow.com/questions/45569418/how-to-use-boost-context-corre… But I'm having the crash only with the cross-compiled version, not MSVC. Am I doing something wrong? Or might this be a bug in Fedora's mingw32-boost package?

1 0

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

boost::filesystem and writing to Windows programdata structure
by Tim Burgess 12 Oct '17

12 Oct '17

Hi, I've an application that has been working fine under Windows 7, but I'm now fixing up for running on later Windows versions. I've been hitting unhandled exceptions when writing to c:\programdata\(my company)\(my app name)\ and understand that this is due to the permissions for such folders being more restrictive on Windows 8, 8.1 and 10. My research seems to indicate that I can modify my installer to set up my folders with appropriate permissions at install-time, but I'd prefer to use boost::filesystem to check folder/file permissions then change them at run-time, if necessary using appropriate csidl values. Can anybody offer any advice, please? Best wishes. Tim Burgess

4 5

[stacktrace] Trace information from GetExceptionInformation()?
by Nat Goodspeed 11 Oct '17

11 Oct '17

In an __except() filter expression (Microsoft Structured Exception), it's legal to call GetExceptionInformation() to retrieve a pointer to an _EXCEPTION_POINTERS struct. A little bit of Google searching turned up a few recipes for walking the stack information indirectly provided by that _EXCEPTION_POINTERS data. Would it be reasonable to have a Microsoft-specific stacktrace constructor accepting _EXCEPTION_POINTERS*? Or perhaps a factory function? I would like to be able to capture the platform-specific _EXCEPTION_POINTERS information, but then, once I have it in hand, engage the rest of the Boost.Stacktrace functionality. Apologies if this has already been asked and answered. If so, please simply point me to the previous discussion. Thank you!

2 1

boost::interprocess::managed_mapped_file filename
by Markus Bonk 10 Oct '17

10 Oct '17

Hi, Unfortunately wmanaged_mapped_file constructors use char instead of wchar for the filename. This causes big problems on windows where %appdata% and %localappdata% include the user name which may include Unicode characters that after conversion result in the windows ‘A’ methods failing to find the referenced file. I don’t know of any work around except using Unicode filenames. Does anyone know of a way around this. Are there any plans of making wmanaged_mapped_file use wchar for the filenames? Markus ________________________________ Markus Bonk Senior Software Engineer [cid:imageac7178.GIF@91f798f8.4ca4a8b2] 3Dconnexion GmbH Clarita-Bernhard-Str. 18 81249 München Germany Tel: +49 (89) 897 45 42 - 70 Fax: +49 (89) 897 45 42 - 50 markus_bonk(a)3dconnexion.com<mailto:markus_bonk@3dconnexion.com> www.3dconnexion.com<http://www.3dconnexion.com> Geschäftsführer: Antonio Pascucci Sitz der Gesellschaft: München Registergericht: München HRB 99232

1 0

Compiling boost with optional _GLIBCXX_DEBUG support
by Jayesh Badwaik 09 Oct '17

09 Oct '17

Hi, How to compile boost so that compilation of user programs both with _GLIBCXX_DEBUG and without _GLIBCXX_DEBUG is supported? Currently, if I compile boost with _GLIBCXX_DEBUG then I cannot compile my programs without this flag, and vice versa. The actual error comes from program_options attached in a file. I gather from the interweb that the error is well known, however, I could not find instructions to compile boost such that both options are supported. -- Cheers Jayesh Badwaik https://www.jayeshbadwaik.in

2 2

[review] The review period of Boost.DoubleEnded has ended -- thanks to all involved
by Thorsten Ottosen 09 Oct '17

09 Oct '17

Dear users and members of Boost, We are now done with the review of Benedek Thaler's Boost.DoubleEnded library. Many thanks to all those involved in discussions and reviews. It will take me some time to digest all the feedback and get back with the review results. kind regards Thorsten, review manager -- Best regards, Thorsten Jørgen Ottosen, Ph.D. Director of Research +45 23308797 Dezide (www.dezide.com)

1 0

[asio] "reverse" stream?
by Phil Sean 07 Oct '17

07 Oct '17

Hi, Is there a stream (or other implementation) in asio that reverses the next layer and the read()/write() layer of another stream? For example, a reverse ssl::stream would send/receive data in clear text, but read()/write() operations should rather expect encrypted data. Thanks.

2 1

[geometry] Best Fit Plane
by Manoj Lnu 07 Oct '17

07 Oct '17

Is there a function available in boost geometry to find the best fit plane ? I have a set of 3D points as input. Thanks, Manoj

2 1