July 2014 - Boost-users - lists.stage.boost.cppalliance.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 3

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 2

[statechart] Passing parameters from event to State Local Storage
by Christophe Bourez 16 Nov '16

16 Nov '16

I need to maintain a parameter into the state local storage. This parameter is initially contained in the event that causes the transition to the target state. I give hereafter a small illustrative example. typename sc = boost::statechart; class EvTest : public sc::event<EvTest> { public: EvTest(std::size_t val) : value(val) {} std::size_t getValue() const { return this->value; } private: std::size_t value; }; class MyStateMachine; class StSource; class StTarget; class StSource : public sc::simple_state<StSource, MyStateMachine> { public: typedef sc::custom_reaction<EvTest> reactions; sc::result react(const EvTest &event) { // How to pass event.getValue() to the target state ? transit<StTarget>(); } }; class StTarget : public sc::simple_state<StTarget, MyStateMachine> { public: StTarget(std::size_t val) : val(value) {} private: std::size_t value; }; Thanks, Christophe

3 3

Re: [Boost-users] lexical_cast between double and string slow in Visual Studio 2013
by David Roberts 07 May '15

07 May '15

> That issue is unknown. I'd really appreciate the investigation. I have done some more investigation, and there are two factors that only cause the slowness when they both occur together. > Try excluding the lexical_cast from test, I have a feeling that this is only MSVC related issue: > > #include <sstream> > #include <string> > > int main (int, char **) > { > for (double count = 0.0; count < 1000000.0; count += 1.41) > { > std::stringstream ss; > ss << count; > std::string result = std::move(ss.str()); > ss.str(std::string()); > > ss << result; > ss >> count; > } > > return 0; > } > Running your test program does not exhibit the problem. It runs in around 3 seconds on my machine when built with either Visual Studio 2010 or Visual Studio 2013. However, changing it very slightly to match more closely what lexical_cast does internally does recreate the problem: #include <sstream> #include <string> int main (int, char **) { for (double count = 0.0; count < 1000000.0; count += 1.41) { std::stringstream ss; ss.unsetf(std::ios::skipws); ss.precision(17); ss << count; std::string result = std::move(ss.str()); ss.str(std::string()); ss << result; ss >> count; } return 0; } The effect of setting the precision to 17 is that lots of 9s appear in the string representations. (The number 17 is what boost::detail::lcast_get_precision(double*) chooses.) Without the precision call the contents of the string called result start off like this: 0 1.41 2.82 4.23 5.64 7.05 8.46 9.87 11.28 12.69 With precision set to 17 they start off like this: 0 1.4099999999999999 2.8199999999999998 4.2299999999999995 5.6399999999999997 7.0499999999999998 8.4599999999999991 9.8699999999999992 11.279999999999999 12.69 This happens for both Visual Studio 2010 and Visual Studio 2013. Then the next difference is that Visual Studio 2013 spends a lot longer handling all the extra 9s. Changing the program so that the double is converted to a string using std::stringstream without a precision call and then back to double using lexical_cast takes about 3 seconds for both Visual Studio 2010 and Visual Studio 2013. It is the combination of having all the extra 9s to parse and using Visual Studio 2013 that makes the test using lexical_cast to go both ways slow. Both Visual Studio 2010 and Visual Studio 2013 do the conversion by calling std::num_get<char,std::istreambuf_iterator<char,std::char_traits<char> > >::do_get() which then calls a function called _Stodx() which is implemented in xstod.c. This function is very different for the two versions. In Visual Studio 2010 it's a relatively thin wrapper around the C function strtod(). In Visual Studio 2013 _Stodx() has got a completely new implementation that's generated by #including xxstod.h with some macros defined. The original C function strtod() is much faster than the new _Stodx() when there are lots of 9s at the end of the strings being parsed. This modification to the program: #include <sstream> #include <string> #include <stdlib.h> int main (int, char **) { for (double count = 0.0; count < 1000000.0; count += 1.41) { std::stringstream ss; ss.unsetf(std::ios::skipws); ss.precision(17); ss << count; std::string result = std::move(ss.str()); ss.str(std::string()); ss << result; char *endptr; count = strtod(ss.str().c_str(), &endptr); } return 0; } has a runtime of about 3 seconds even though it's got to cope with all the 9s. I guess only someone from Microsoft or Dinkumware could comment on why _Stodx() was reimplemented. But the other thing is that by setting precision to 17 lexical_cast is bloating the string representations of the doubles with lots of 9s in both Visual Studio 2010 and Visual Studio 2013. Setting precision to 15 instead prevents this, and makes the original test run faster even with Visual Studio 2013 (about 4 seconds rather than 10). Regards, David

2 1

Statechart serialization
by mbrodeur65 04 Mar '15

04 Mar '15

Hi, I'm looking for a solution to serialize boost::statechart objects. I'm aware that this feature is on the statechart library todo list but was wondering if there are any workaround to achieve this with the latest boost release (1.34) ? thanks for your help ! mbrodeur65 -- View this message in context: http://www.nabble.com/Statechart-serialization-tf4131326.html#a11749139 Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

NT² 3.0 and Boost.SIMD - Stable release
by Joel Falcou 21 Nov '14

21 Nov '14

The first stable release of the 3.x series of MetaScale’s open-source software is available: NT² 3.0. It also includes its spin-off project, Boost.SIMD (not yet a Boost library). Many Issues have been closed since last beta. The main focus of this release cycle was to fix performances issues and to stabilize some parts of the API. Next step will be to separate NT2 and Boost.SIMD into separate repositories, thus making one more step toward Boost.SIMD submission into review. [ http://www.metascale.org/nt%C2%B2-3-0-and-boost-simd ] *Changes & Bug Fixes:* - Major performance improvements in both libraries - Added experimental support for the HPX runtime for parallelization on shared memory systems - Optimizations of many elemental functions, in particuler log/ex, frexp/ldexp and cbrt - More advanced shuffle pattern recognition for SIMD - Fixed issues with Visual Studio 2013 - More functions are force-inlined to ensure good performance - New functions for conversion between types and mixing of vectors of different sizes - Demo applications usable as benchmarks - Better handling of errors when an unsupported function is called - New API for custom memory allocators Full changelog is available at https://github.com/MetaScale/nt2/releases/tag/3.0.0. *How to get it ?* - Source and binary packages can be downloaded here: http://nt2.metascale.org/downloads - The release is also available on Github : https://github.com/MetaScale/nt2/releases - The main master branch is still under development : https://github.com/MetaScale/nt2

2 4

[Thread] Read-write locks
by lfrfly＠icqmail.com 18 Sep '14

18 Sep '14

I'm trying to create a standard read/write lock using Boost Threads, and I'm having a bit of difficulty mapping the Boost concepts onto the usual ones. A read/write lock should have several states: Locked for reading (multiple threads may lock at once), locked for writing (only one thread may lock, and no threads may be locked for reading at the same time), and unlocked. Ideally it would be nice if an RWL which is locked for reading may temporarily upgrade to locked for writing, then return to the locked for reading state. Boost supports several relevant notions of locking: shared locking, upgrade locking, and exclusive locking. This to me is a confusing distinction. In particular, a shared_mutex seems appropriate as the basis for a RWL, but is lock_upgrade() the equivalent of a write lock and lock_shared the equivalent of a read lock? This is unclear. If "upgrade locking" is not the same as "exclusive locking", then is an upgrade lock actually exclusive? Could someone please clarify this.

1 0

[1.56.0] Release candidates available
by Marshall Clow 04 Aug '14

04 Aug '14

Release candidate files for 1.65.0 are available at http://boost.cowic.de/rc/ 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. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost_1_56_0_rc1.7z) = 0ac22b92b24209286d48e4c41925cd9f MD5 (boost_1_56_0_rc1.tar.bz2) = 5b5bfa99244b1ac5737323decceb19c2 MD5 (boost_1_56_0_rc1.tar.gz) = 2047cdd4e09cda34e7f10fec0f821175 MD5 (boost_1_56_0_rc1.zip) = 0c544f6acc85550b15cdc9221f2ac0c9 Thanks! -- The release managers

3 4

[serialization] Please help me solve this compile error.
by Paul Blampspied 04 Aug '14

04 Aug '14

I am tearing my hair out over this, partly because I believe the code used to compile. I just can't see what the problem is. I enclose all the pertinent code as I cannot say which bits are irrelevant. There are two classes: ManagedArray which is an array of data without size or capacity data (this is stored elsewhere). PersistentManagedArray which I wrote to enable ManagedArrays to be serialized. The error message is produced in 'main': error: no match for 'operator<<' in 'oa << PersistentManagedArray<int>((* & size), (* & capacity), (* & ints))' It seems to me that I have defined the necessary serialize member function with the right signature. Commented out is code I wrote some time ago which used separate load and save functions. This, I believe, used to work. #include <fstream> #include <boost/archive/binary_oarchive.hpp> #include <boost/archive/binary_iarchive.hpp> #include <string> using namespace std; //**************************************************************************************************************************** template<class T> class ManagedArray { public: T *values; ManagedArray() { values = NULL; } ~ManagedArray() { if (values) { delete [] values; } } //Changes array size. If array grows, the new values are unintialized. void resize(unsigned oldSize, unsigned newSize) { if (oldSize==newSize) return; T *newValues = (newSize==0) ? NULL : new T[newSize]; if (oldSize!=0) { T *oldValue, *newValue; T *end = values + (oldSize<newSize ? oldSize : newSize); for(oldValue=values, newValue=newValues; oldValue<end; oldValue++, newValue++) { *newValue = *oldValue; } } if (values) { delete [] values; } values = newValues; } //Changes array size. If array grows, the new values are initialised to copies of a prototype, initValue. void resize(unsigned oldSize, unsigned newSize, T &initValue) { if (oldSize==newSize) return; T *newValues = (newSize==0) ? NULL : new T[newSize]; T *oldValue = values; T *newValue = newValues; if (oldSize!=0) { T *oldEnd = values + (oldSize<newSize ? oldSize : newSize); for(; oldValue<oldEnd; oldValue++, newValue++) { *newValue = *oldValue; } } T *newEnd = newValues + newSize; for(; newValue<newEnd; newValue++) { *newValue = initValue; } delete [] values; values = newValues; } inline T &operator[](unsigned index) { return values[index]; } inline const T &operator[](unsigned index) const { return values[index]; } }; //**************************************************************************************************************************** //This class helps to save a ManagedArray in a Boost archive // Usage: // ar & PersistentManagedArray(size, capacity, array); template<class T> class PersistentManagedArray { public: PersistentManagedArray(unsigned &size, unsigned &capacity, ManagedArray<T> &managedArray) : _size(size), _capacity(capacity), _managedArray(managedArray) {valueArrayExists = (_managedArray.values!=NULL);} private: unsigned &_size; unsigned &_capacity; ManagedArray<T> &_managedArray; bool valueArrayExists; friend class boost::serialization::access; // template<class Archive> // void save(Archive & ar, const unsigned int version) const { // ar & valueArrayExists; // if (valueArrayExists) { // for(unsigned i=0; i<_size; i++) { // ar & _managedArray.values[i]; // } // } // } // template<class Archive> // void load(Archive & ar, const unsigned int version) { // _managedArray.values = NULL; // ar & valueArrayExists; // if (valueArrayExists) { // _managedArray.resize(0, _capacity); // for(unsigned i=0; i<_size; i++) { // ar & _managedArray.values[i]; // } // } // } // BOOST_SERIALIZATION_SPLIT_MEMBER() template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & valueArrayExists; ar & _size; ar & _capacity; if (Archive::is_loading::value) { delete _managedArray.values; _managedArray.values = new T[_capacity]; } for(unsigned i=0; i<_size; i++) { ar & _managedArray.values[i]; } } }; int main(int argc, char *argv[]) { ManagedArray<int> ints; unsigned size; unsigned capacity; string fileName = "data.xxx"; ofstream file(fileName.c_str(), ios::out|ios::binary); if (file.good()) { boost::archive::binary_oarchive oa(file); oa << PersistentManagedArray<int>(size, capacity, ints); //This line does not compile ! } }

1 0

[MultiIndex] Indexing integers
by Sensei 31 Jul '14

31 Jul '14

Dear all, I am experimenting with MultiIndex, and I am happy with my custom classes. Now I am wondering, can I index integers without a custom class? For instance, say we have a 32 bit unsigned integer, how can I index these with respect to the MSB or LSB? My first guess is using a union, something like union uint32_u { uint32_t data; uint16_t bits[2]; }; // define a multiply indexed set with indices by id and name typedef boost::multi_index::multi_index_container< uint32_u, boost::multi_index::indexed_by< // sort by MSB boost::multi_index::ordered_non_unique<boost::multi_index::member<employee, uint16_t, uint32_u.bits[0]>>, // sort by LSB boost::multi_index::ordered_non_unique<boost::multi_index::member<employee, uint16_t, uint32_u.bits[1]>>, > > integer_set; But I cannot obviously compile it. Is there a way I can do this? Thanks!

2 1