- Boost - lists.preview.boost.org

Any-Range containing transformed range fails when compiled with optimizations
by Auer, Jens 17 Jan '16

17 Jan '16

Hi, I have a program which produces different results based on the compiler options. The program uses a boost::any_range containing a transformed range where the transformation function just returns a new object of a simple struct: #include <vector> #include <boost/range.hpp> #include <boost/range/any_range.hpp> #include <boost/range/adaptor/transformed.hpp> #include <iostream> template<typename T1, typename T2> void ASSERT_EQ(T1 x,T2 y) {assert(x == y);}; struct SourceEvent { std::uint32_t event; void* ptr; }; int main() { using boost::adaptors::transformed; using R = boost::any_range<SourceEvent, boost::forward_traversal_tag, SourceEvent, std::ptrdiff_t>; std::vector<std::int32_t> v(100); R r = v | transformed( [](auto const&) {return SourceEvent{0u, nullptr};} ); auto t = v | transformed( [](auto const&) {return SourceEvent{0u, nullptr};} ); ASSERT_EQ( 100u, boost::size(r) ); ASSERT_EQ( 100u, boost::size(t) ); for (auto const& i: t) { ASSERT_EQ(0u, i.event ); ASSERT_EQ(nullptr, i.ptr); } for (auto const& i: r) { ASSERT_EQ(0u, i.event ); ASSERT_EQ(nullptr, i.ptr); } std::cout << "OK" << std::endl; return 0; } When compiled without optimization, it just prints ok. The same source compiled with optimizations asserts, and prints some interesting warnings: In file included from /usr/local/boost-1.60.0/include/boost/range/detail/any_iterator.hpp:22:0, from /usr/local/boost-1.60.0/include/boost/range/any_range.hpp:17, from prog.cc:3: /usr/local/boost-1.60.0/include/boost/range/detail/any_iterator_wrapper.hpp: In member function 'boost::range_detail::any_forward_iterator_wrapper<WrappedIterator, Reference, Buffer>::reference boost::range_detail::any_forward_iterator_wrapper<WrappedIterator, Reference, Buffer>::dereference() const [with WrappedIterator = boost::iterators::transform_iterator<boost::range_detail::default_constructible_unary_fn_wrapper<main()::<lambda(const auto:1&)>, SourceEvent>, __gnu_cxx::__normal_iterator<int*, std::vector<int> >, boost::iterators::use_default, boost::iterators::use_default>; Reference = SourceEvent; Buffer = boost::any_iterator_buffer<64ul>; boost::range_detail::any_forward_iterator_wrapper<WrappedIterator, Reference, Buffer>::reference = SourceEvent&]': /usr/local/boost-1.60.0/include/boost/range/detail/any_iterator_wrapper.hpp:302:57: warning: function may return address of local variable [-Wreturn-local-addr] return dereference_cast<reference>(*m_it); ^ /usr/local/boost-1.60.0/include/boost/range/detail/any_iterator_wrapper.hpp:302:52: note: declared here return dereference_cast<reference>(*m_it); ^ prog.exe: prog.cc:7: void ASSERT_EQ(T1, T2) [with T1 = unsigned int; T2 = unsigned int]: Assertion `x == y' failed. Aborted The example is compiled with gcc 5.2 and boost 1.60 (http://melpon.org/wandbox/permlink/QF1qyw5bWHKwyKJ8) Is there an error in my code? I would guess that transforming a range into a range of new objects of another type is quite common, so it should work. I am also curious why the warning is only emitted when compiling with optimizations. Best wishes, Jens -- Jens Auer | CGI | Software-Engineer CGI (Germany) GmbH & Co. KG Rheinstraße 95 | 64295 Darmstadt | Germany T: +49 6151 36860 154 jens.auer(a)cgi.com<mailto:jens.auer@cgi.com> Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail.

3 7

Re: [boost] [gsoc16] Can I quickly check if the below really is the best approach?
by Shangtong Zhang 16 Jan '16

16 Jan '16

Hi, > // At global scope, allocates no memory whatsoever > static const constexpr static_map<int, const char *> map { > { 5, "apple" }, > { 8, "pear" }, > { 0, "banana" }, > ... > }; > // Works, constexpr "apple" > constexpr const char *what_is_5 = map[5]; > // Works > assert(map[5] && !strcmp(map[5], "apple"); > // Works > map[5]="orange"; > assert(map[5] && !strcmp(map[5], "orange"); > // Throws exception as there is no key 6 > map[6]; > map.at <http://map.at/>(6); I have difficulty understanding this, As variable map is const and constexpr, how can map[5]=“orange” work? I don’t know how to implement this, where to store the “orange”. Could anyone help me? Thanks, Shangtong Zhang, Senior Student, School of Computer Science, Fudan University, PRC.

2 1

[gsoc16]Interest in static map
by Shangtong Zhang 15 Jan '16

15 Jan '16

Hi Niall Douglas, I’m interested in the project static map and want to contribute to it in gsoc 2016. And I try to start with the programming competency test. Following is what I have done, https://github.com/ShangtongZhang/StaticMap/blob/master/main.cpp <https://github.com/ShangtongZhang/StaticMap/blob/master/main.cpp> Could you please give me some advice? In addition, I’m a little confused with // This should fail elegantly and usefully ... //constexpr std::array<unsigned, 0> string_hashes_fail = hash_strings(5); My understanding is that it will raise a run-time exception, is it right? Thanks, Shangtong Zhang, Senior Student, School of Computer Science, Fudan University, PRC.

2 1

Is there interest in Computable Calculus?
by Damian Vicino 15 Jan '16

15 Jan '16

Hi, I’m interested in developing basic support of “real numbers” for computable calculus applications. In computable calculus, reals have infinite precision (certain restrictions may apply). The usual approach is representing numbers as functions producing digits. An arithmetic operation produces a new function using the functions in the operands and some simple expression manipulations. When a number needs to be evaluated (e.g., for comparisons where expression rules are unknown), enough digits for reaching an answer are generated using the functions. For example, 3.14 < pi requires generating 3 digits to answer “true”. The algorithms for arithmetic operations and evaluation are well known, and multiple implementations were developed (mostly in the 90s). However, I couldn’t find an open source implementation and had to come up with my own for working in a project during the last 2 years. My preferred reference for the required algorithms is the book: Aberth, Oliver. Computable Calculus. Academic Press, 2001. In particular, my initial scope would be the 4 arithmetic operations (+, -, *, /), and the comparison operators (<, =) for reals. Someone is interested in such a library in boost?

4 4

IS THERE A WAY TO FIND IF A CERTAIN TYPE HAS A CERTAIN MEMBER?
by Juan Dent 15 Jan '16

15 Jan '16

> HI, > > > I have read that via enable_if and other constructs, one can declare a member of a type conditionally. > > What I need is a way to be able to test whether a certain type has a certain method or member data, so that I can call it or use it accordingly. > > Does boost have something like this?? > > > Regards, > Juan

4 3

a safe integer library
by Robert Ramey 14 Jan '16

14 Jan '16

Arithmetic operations in C++ are NOT guaranteed to yield a correct mathematical result. This feature is inherited from the early days of C. The behavior of int, unsigned int and others were designed to map closely to the underlying hardware. Computer hardware implements these types as a fixed number of bits. When the result of arithmetic operations exceeds this number of bits, the result will not be arithmetically correct. I have crafted a library to address this issue once and for all. You can find out more about this by checking out the page for Safe Numerics at the boost library incubator. www.blincubator.com I hereby request that this library be added to the boost review queue. I've also made a proposal for the C++ Standards committee to include a simplified version of this library as part of he C++ standard. You can see the proposal at http://www.rrsd.com/software_development/safe_numerics/proposal.pdf Robert Ramey

14 42

ATTENTION: Library requirements..
by Rene Rivera 13 Jan '16

13 Jan '16

Last Summer I brought up the subject of library organization requirements to make it easier to write the development and release tools needed to keep the Boost machine going. See this thread < http://lists.boost.org/Archives/boost/2015/06/223027.php> for a refresher. This morning I committed the first part of the above.. A new set of library requirements that take into account existing practices. Adds some additional integration requirements. And puts in limits to reduce some integration burdens. Please read the new requirements carefully < http://www.boost.org/development/requirements.html#Requirements>. It would be wonderful if authors start making changes as needed immediately. But at some point I, and possible others, will start making changes to all libraries to follow the requirements. So that the release, build, and testing teams can move forward with better support. And of course, more cleanups and such will follow. Hopefully before the next release is out the door. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

16 80

[BPM] Supporting an alternative to meta/libraries.json
by Louis Dionne 13 Jan '16

13 Jan '16

Dear list, Currently, all Boost libraries are required to have a meta/libraries.json file at their root, which contains some meta-data describing the library. As I understand it, this meta-data is then used to generate the list of all libraries with their description when a release is done. I find having such a directory at the root of every library annoying, since it clutters it. Furthermore, for metaprogramming libraries, the name can be slightly confusing since meta/ might be expected to contain something different. I propose that we allow libraries to specify their metadata in a `.boost` file located at their root. Using a dotfile is the most common way of providing information for an external service (for example .travis.yml), and dotfiles are usually more discrete when viewing the project in an editor. Furthermore, making `boost` part of the filename is more descriptive. I have submitted a pull request to BPM [1] adding the ability to fetch the meta data in a .boost file. The meta-data can still be provided in meta/libraries.json, so this should not affect existing libraries. Related questions that we might want to consider: - Should it be .boost.json instead of .boost? - Perhaps we could store the meta-data for all the libraries in the same place, and get rid of the individual meta-data files? - If this suggestion is accepted, is there more to modify than BPM? Regards, Louis [1]: https://github.com/boostorg/bpm/pull/1

5 19

[test] BOOST_TEST macro and std::max
by Benedek Thaler 13 Jan '16

13 Jan '16

Hi, I'd expect the following cheks to pass: BOOST_TEST(3u == (std::max)(0u, 3u)); BOOST_TEST(3u == ((std::max)(0u, 3u))); But both fails with: check 3u == ((std::max)(0u, 3u)) has failed [3 != 7095312] Did I miss something regarding BOOST_TEST usage? Platform: Linux, GCC 5.3, Boost 1.60 Thanks, Benedek

4 15

Re: [boost] asio config.hpp macro redefinition - mistake?
by Curdeius Curdeius 13 Jan '16

13 Jan '16

> > ---------- Wiadomość przekazana dalej ---------- > From: "John M. Dlugosz" <mpbecey7gu(a)snkmail.com> > To: boost(a)lists.boost.org > Cc: > Date: Tue, 12 Jan 2016 17:32:48 -0600 > Subject: [boost] asio config.hpp macro redefinition - mistake? > In file boost_1_59_0\boost\asio\detail\config.hpp line 227 gives a macro > redefinition warning. > (...) > It seems that this is missing a guard or has the if/else things mixed up. > This was fixed some time ago. See https://github.com/boostorg/asio/commit/b9cb61416e1972d7490d91da91df549703f… . Regards, Marek Kurdej

1 0

[fusion]enabler.hpp junk character at start of file
by Aparna Kumta 13 Jan '16

13 Jan '16

All accumulator tests fail when compiled with Oracle Solaris Studio in 'dev' branch as follows: "../boost/fusion/support/detail/enabler.hpp", line 1: Error: A declaration was expected instead of "???". 1 Error(s) and 1 Warning(s) detected. See http://www.boost.org/development/tests/develop/developer/output/oracle-spar… It appears that in file boost/fusion/support/detail/enabler.hpp, there is some junk character at the start of file. This cannot be observed via vi editor, but with ' head -1 enabler.hpp', this can be seen. % head -1 enabler.hpp ��/*===================================== Perhaps these characters should be removed? When I view the file on github, I do not see the issue, however when I try to edit the file, I see it. Will submit a PR. Thanks, Aparna

2 2

[regression] Regression tests for 'develop' has error
by Edward Diener 13 Jan '16

13 Jan '16

Trying to open the regression test results for 'develop' page gives: "Error extracting file: Error code 3 - A severe error in the zipfile format was detected." This has happened numerous times before. Can this be fixed, not only now but permanently ? Surely there must be some way of determining why the zipfile format has a severe error and preventing this in the future.

5 16

asio config.hpp macro redefinition - mistake?
by John M. Dlugosz 13 Jan '16

13 Jan '16

In file boost_1_59_0\boost\asio\detail\config.hpp line 227 gives a macro redefinition warning. // Compliant C++11 compilers put noexcept specifiers on error_category members. #if !defined(BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT) # if (BOOST_VERSION >= 105300) # define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT BOOST_NOEXCEPT # elif defined(__clang__) # if __has_feature(__cxx_noexcept__) # define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT noexcept(true) # endif // __has_feature(__cxx_noexcept__) # elif defined(__GNUC__) # if ((__GNUC__ == 4) && (__GNUC_MINOR__ >= 7)) || (__GNUC__ > 4) # if defined(__GXX_EXPERIMENTAL_CXX0X__) # define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT noexcept(true) # endif // defined(__GXX_EXPERIMENTAL_CXX0X__) # endif // ((__GNUC__ == 4) && (__GNUC_MINOR__ >= 7)) || (__GNUC__ > 4) # endif // defined(__GNUC__) # if defined(BOOST_ASIO_MSVC) # if (_MSC_VER >= 1900) # define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT noexcept(true) // ****** here ****** # endif // (_MSC_VER >= 1900) # endif // defined(BOOST_ASIO_MSVC) # if !defined(BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT) # define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT # endif // !defined(BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT) #endif // !defined(BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT) To paraphrase, the block reads # if (BOOST_VERSION >= 105300) // it is: 105900 >= 105300 *# define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT BOOST_NOEXCEPT* ⋮ # if defined(BOOST_ASIO_MSVC) # if (_MSC_VER >= 1900) *# define BOOST_ASIO_ERROR_CATEGORY_NOEXCEPT noexcept(true)* # endif // (_MSC_VER >= 1900) # endif // defined(BOOST_ASIO_MSVC) It seems that this is missing a guard or has the if/else things mixed up.

2 1

[property_tree] Still being maintained?
by Gavin McNiff 12 Jan '16

12 Jan '16

Hi, I was wondering if the Property_Tree library is still being actively maintained. There are 9 GitHub pull requests stacked up since the summer? Best regards Gavin McNiff

2 2

[err] RFC
by Domagoj Saric 11 Jan '16

11 Jan '16

https://github.com/psiha/err README.md copy-paste: --------------------------------------------- err - yet another take on C++ error handling. We have throw and std::error_code, what more could one possibly want? --------------------------------------------- std::error_code&co tried to solve or at least alleviate the problem of overhead of using exceptions (in terms of both source code verbosity and binary code size&speed) with functions which need to report failures that need not be 'exceptional' depending on the context of the call (thereby requiring try-catch blocks that convert exceptions to 'result codes'). Unfortunately, the way it was finally implemented, std::error_code did not quite accomplish what it set out to do: • in terms of runtime efficiency: 'manual'/explicit EH (try-catch blocks) is no longer needed but the compiler still has to insert hidden EH as it has to treat the functions in question as still possibly throwing (in fact the implementation/codegen of functions which use std::error_code for error reporting becomes even fatter because it has to contain both return-on-error paths and handle exceptions) • in terms of source code verbosity: again, try-catch blocks are gone but separate error_code objects have to be declared and passed to the desired function. Enter boost::err: 'result objects' (as opposed to just result or error codes) which can be examined and branched upon (like with traditional result codes) or left unexamined to self-throw if they contain a failure result (i.e. unlike traditional result codes, they cannot be accidentally ignored). Thanks to latest C++ language features (such as r-value member function overloads) incorrect usage (that could otherwise for example lead to a result object destructor throwing during a stack-unwind) can be disallowed/detected at compile time. Discussions where the concept (or a similar one) was first concieved of and/or so far discussed: • http://boost.2283326.n4.nabble.com/system-filesystem-v3-Question-about-erro… • http://cpptips.com/fallible • https://github.com/ptal/std-expected-proposal • https://github.com/ptal/expected • https://github.com/adityaramesh/ccbase/blob/master/include/ccbase/error/exp… • http://stackoverflow.com/questions/14923346/how-would-you-use-alexandrescus… • https://svn.boost.org/trac/boost/wiki/BestPracticeHandbook#a8.DESIGN:Strong… • http://2013.cppnow.org/session/non-allocating-stdfuturepromise **************************************************************** For starter's, to reduce the length of the first post, I'll assume that everyone as at least somewhat familiar with similar/related proposals from Andrei Alexandrescu (std::expected) and Niall Douglas (std::monad) to which I gave links above. What, primarily, makes (Boost.)Err different from other proposals is the ability to (using latest C++ features) detect/distinguish between temporaries and 'saved' return values by using two different class templates (result wrappers), fallible_result (for rvalues) and result_or_error (for lvalues) and thus minimise or often completely eliminate any extra verbosity: If we had a function foo() that produces bar_t objects but can fail with an err_t, up till now we had two options: * bar_t foo() throw( err_t ); * optional<bar_t> foo( err_t & ); Err enables the library writer to write a single API and a single implementation: err::fallible_result<bar_t, err_t> foo(); where fallible_result is the class template that wraps temporaries/rvalues returned from functions and its member functions are all declared with && (i.e. callable only on rvalues) so you get a compiler error if you save it to an auto value and try to do anything with it. The two exceptions are the implicit conversion operators to: - bar_t, which will either return bar_t or throw err_t and which is used for the 'EH code path' bar_t my_bar( foo() ); - err::result_or_error<bar_t, err_t> which is used for the 'oldsk00l nothrow error code path' err::result_or_error<bar_t, err_t> maybe_bar( foo ); if ( maybe_bar ) { print( *maybe_bar ); } else { log( maybe_bar.error() ); } Also, if the fallible_result rvalue is left uninspected and contains an error its destructor will throw (which AFAICT should be safe considering it is an rvalue and no other exception can possibly be active at the same time) - this makes code that uses Err enabled libraries/APIs but relies on EH almost indistinguishable from 'classic EH' APIs (almost because the one difference that remains is with the immediate use of the return value: because of the wrapper class one can no longer write foo().do_something() but has to implicitly use the -> operator and write foo()->do_something() where the -> operator will check-and-throw if foo() did not succeed). To wrap up, this approach gives the user the immediate and fine grained control over which error handling mechanism he/she wants to use while allowing the developer to write a single API and implementation - AFAICT it is a no brainer replacement for <system_error>, it is less verbose and much more efficient ;-) ps. the small library @ https://github.com/psiha/err is by no means a finished product, it contains no tests or documentation but 'it works' (i.e. it is used in the, also upcoming, https://github.com/psiha/mmap)...I'm bringing it to public view for scrutiny, discussion and guidance lest I steer in the wrong direction ;) -- "What Huxley teaches is that in the age of advanced technology, spiritual devastation is more likely to come from an enemy with a smiling face than from one whose countenance exudes suspicion and hate." Neil Postman

4 20

Add Boost.Convert to the Trac
by Vicente J. Botet Escriba 11 Jan '16

11 Jan '16

Hi, I have requested this (https://svn.boost.org/trac/boost/ticket/11814) 6 weeks ago without response. Is anyone maintaining the Trac component? I see Doug Gregor, but I believe he is not actively working on Boost. Best, Vicente

2 2

[trac] boost 1.61
by Raffi Enficiaud 11 Jan '16

11 Jan '16

Hi all, Would it be possible to add 1.61 to the roadmap? Thanks, Raffi

2 1

want to contribute in boost c++ organisation
by Aman Varshney 11 Jan '16

11 Jan '16

As I am a 2nd year computer Science student at IIIT-Hyderabad. Being a beginner I have some idea about C++ and want to start contributing to open source. I found the boost c++library. It would be great if I get some directions from you as to where to start from. Thank You

1 0

[regression] Summary for develop is unavailable
by Antony Polukhin 08 Jan '16

08 Jan '16

Hi, At http://www.boost.org/development/tests/develop/developer/summary.html you'll find "Error extracting file: Error code 3 - A severe error in the zipfile format was detected." Please, could someone fix that? -- Best regards, Antony Polukhin

1 1

Ynt: Building Boost (1.60) with Clang and NDK
by Fatih Kıralioğlu 07 Jan '16

07 Jan '16

Ok, I am sharing my build.bat user-config-android.jam file below, from the outputs, clang is using mingw headers, for clang build, is mingw headers really necessary? build.bat: set CXXFLAGS="-I%ANDROID_NDK%/platforms/android-9/arch-arm/usr/include -I%ANDROID_NDK%/sources/cxx-stl/gnu-libstdc++/4.9/include -I%ANDROID_NDK%/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi/include" set TOOLSET=gcc-android b2 --toolset=%TOOLSET% --user-config=./user-config-android.jam cxxflags=%CXXFLAGS% threadapi=pthread --prefix=..\boost_android_arm --builddir=./ target-os=linux --with-date_time --with-filesystem --with-regex --with-log define=BOOST_FILESYSTEM_VERSION=3 --with-program_options --with-signals --with-system --with-thread link=static runtime-link=shared threading=multi install user-config-android.jam: androidNDKRoot = android-ndk-r10e ; # put the relevant path using clang : android : $(androidNDKRoot)/toolchains/llvm-3.6/prebuilt/windows-x86_64/bin/clang++ : <compileflags>--sysroot=$(androidNDKRoot)/platforms/android-21/arch-arm <compileflags>-Os <compileflags>-fno-strict-aliasing <compileflags>-O2 <compileflags>-DNDEBUG <compileflags>-g <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/gnu-libstdc++/4.9/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi/include <compileflags>-D__GLIBC__ <compileflags>-D__ANDROID__ <compileflags>-D_GLIBCXX__PTHREADS <compileflags>-D__arm__ <compileflags>-D_REENTRANT And I'am getting this error: g++: error: unrecognized command line option '-stdlib=libc++' clang++.exe: error: linker (via gcc) command failed with exit code 1 (use -v to see invocation) "android-ndk-r10e/toolchains/llvm-3.6/prebuilt/windows-x86_64/bin/clang++" -o "bin.v2\libs\date_time\build\clang-linux-andr oid\release\target-os-android\threadapi-pthread\threading-multi\libboost_date_time-clang-mt-1_60.so.1.60.0" -Wl,-soname -Wl,libboost_date_time-clang-m t-1_60.so.1.60.0 -shared -Wl,--start-group "bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-mult i\gregorian\greg_month.o" "bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\gregorian\greg_ weekday.o" "bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\gregorian\date_generators.o" -Wl,-Bstatic -Wl,-Bdynamic -Wl,--end-group -stdlib=libc++ -lc++_shared -Landroid-ndk-r10e/sources/cxx-stl/llvm-libc++/libs/ar meabi ...failed clang-linux.link.dll bin.v2\libs\date_time\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\libboost_da te_time-clang-mt-1_60.so.1.60.0... ...skipped <p..\boost_android_arm\lib>libboost_date_time-clang-mt-1_60.so.1.60.0 for lack of <pbin.v2\libs\date_time\build\clang-linux-android\release \target-os-android\threadapi-pthread\threading-multi>libboost_date_time-clang-mt-1_60.so.1.60.0... clang-linux.compile.c++.without-pth bin.v2\libs\system\build\clang-linux-android\release\target-os-android\threadapi-pthread\threading-multi\error_cod e.o In file included from libs\system\src\error_code.cpp:16: In file included from .\boost/system/error_code.hpp:19: In file included from android-ndk-r10e/sources/cxx-stl/gnu-libstdc++/4.9/include\ostream:38: In file included from android-ndk-r10e/sources/cxx-stl/gnu-libstdc++/4.9/include\ios:42: In file included from android-ndk-r10e/sources/cxx-stl/gnu-libstdc++/4.9/include\bits/ios_base.h:39: In file included from android-ndk-r10e/sources/cxx-stl/gnu-libstdc++/4.9/include\ext/atomicity.h:35: In file included from android-ndk-r10e/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi/include\bits/gthr.h:148: In file included from android-ndk-r10e/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi/include\bits/gthr-default.h:48: android-ndk-r10e/platforms/android-21/arch-arm/usr/include\pthread.h:164:58: error: unknown type name 'clockid_t'; did you mean ' clock_t'? int pthread_condattr_getclock(const pthread_condattr_t*, clockid_t*) __nonnull((1, 2)); ^ c:/mingw/include\time.h:71:14: note: 'clock_t' declared here typedef long clock_t; Fatih KIRALİOĞLU R&D Engineer fatih.kiralioglu(a)sestek.com www.sestek.com ________________________________________ Gönderen: Fatih Kıralioğlu Gönderildi: 6 Ocak 2016 Çarşamba 21:13 Kime: boost(a)lists.boost.org Konu: Ynt: [boost] Building Boost (1.60) with Clang and NDK Thanks for the responses, The last error I got is: "In file included from libs\date_time\src\gregorian\greg_weekday.cpp:16: In file included from libs\date_time\src\gregorian/greg_names.hpp:14: In file included from .\boost/date_time/gregorian/greg_month.hpp:14: In file included from .\boost/shared_ptr.hpp:17: In file included from .\boost/smart_ptr/shared_ptr.hpp:35: In file included from .\boost/smart_ptr/detail/spinlock_pool.hpp:25: In file included from .\boost/smart_ptr/detail/spinlock.hpp:47: In file included from .\boost/smart_ptr/detail/spinlock_gcc_arm.hpp:12: In file included from .\boost/smart_ptr/detail/yield_k.hpp:28: In file included from .\boost/predef.h:20: In file included from .\boost/predef/hardware.h:14: .\boost/predef/hardware/simd.h:77:5: error: "Multiple SIMD architectures detecte d, this cannot happen!" # error "Multiple SIMD architectures detected, this cannot happen!" " I have also installed and set it as an include dir for b2.exe to use clang and i got the error above fatih ________________________________________ Gönderen: Boost <boost-bounces(a)lists.boost.org> adına Ben Pope <benpope81(a)gmail.com> Gönderildi: 6 Ocak 2016 Çarşamba 19:06 Kime: boost(a)lists.boost.org Konu: Re: [boost] Building Boost (1.60) with Clang and NDK On Wednesday, January 06, 2016 04:06 AM, Fatih Kıralioğlu wrote: > Has anyone built the Boost with Clang and NDK other than CryStax? If so, can you post the related config.jam and build script? I have handled gcc build but clang is very very chalnllenging and no one including the guys in Stackoverflow could answer it. I haven't noticed any problems building boost for Android with the NDK, I honestly have no idea why I see so many people asking how to do it, or patch sets or whatever. I'm using gcc-4.9 and std=c++14 on linux x64 targeting armv7. I package the toolset I want (android 15, gcc-4.9) and pass that sysroot in the CXXFLAGS, I tend not to interfere with the build system of boost or android very much, preferring to drive everything from cmake (for my own projects). What problems have you seen? The NDK is moving entirely to clang, the next release will see gcc deprecated, so I'll have to have a play with moving over to clang, but in my experience, everything I do works equally well on clang for armv7, armv8 and x64. The only problem I remember having is thread locals on iOS targets, but my memory is short, and it only takes a few lines of code to emulate that for most purposes. If you explain what problems you've seen, which libraries, toolsets and command lines, perhaps you'll trigger a memory of a problem I've solved. I can give you more details of my configuration on the weekend, if required. As a sidenote, I'm hoping to bring up a boost/clang/linux/armv8 build bot if and when my Pine64 arrives and I get Ubuntu/Debian running on it (by April if all goes well). I have no idea how quickly it will cycle though, my current x64 tests take around 16 hours for gcc-4.9, gcc-5.2 and clang-3.7, I'll probably have to drop gcc-4.9. I had to give up on my regular sanitizer builds on x64 as they just take too long and there seemed to be very little interest. Unfortunately I don't have dedicated machines to run the tests. Ben _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

[review][qvm] QVM formal review report
by Adam Wulkiewicz 07 Jan '16

07 Jan '16

Dear Boost community, The review period for Emil Dotchevski's QVM library has concluded. I'd like to thank everyone who participated in the discussions, esspecially those who sent formal reviews. Only four votes were casted: - 1 vote for acceptance * Rajaditya Mukherjee - 2 votes for conditional acceptance * Rainer Deyke * Oswin Krause - 1 vote for rejection * Phil Endecott However more people commented on issues on the mailing list. Comments received during the course of the review were generally positive, with a number of technical issues identified that need to be addressed. The review identified no fundamental problems in the design or implementation of the library that would entail rejection. The final version of the library can be fully accepted once Emil has addressed the issues identified during the review. Therefore I'm happy to say: Emil Dotchevski's Boost.QVM library is CONDITIONALLY ACCEPTED. Below is a summary of technical concerns: - The identifiers should be made more verbose. This is true both for function names as well as identifers containing "q"/"v"/"m" parts. The former should be replaced with full words, e.g. "transp" -> "transpose". The latter should be replaced at least with "qua"/"quat"/"vec"/"mat" respectively, so e.g. "v_traits" -> "vector_traits"/"vec_traits", "col_m" -> "col_mat", etc. - Many participants found the swizzling syntax using comma operator confusing or not good enough. There were many suggestions about the possible replacements: * v%XY - the old operator% syntax * (v,XY) - the comma operator syntax currently used by QVM * (v,asXY) - in order to limit potential conflicts with macros * XY(v) - function syntax, MOST PREFERED * v.XY() - probably the best but currently not possible (n4165, n4174) * ref(v).XY() * ref(v)[xy] * swizzle(v, xy) * ref(v)->xy The function syntax, i.e. XY(v), was the most prefered solution. Some of the participants appreciated the comma operator as well because of the similarity with shader languages syntax. The library could provide a few alternatives that could be picked by the user, e.g. both a comma and function syntax. - There were concerns regarding deduce_xx set of traits, in particular that traits taking two arguments (deduce_q2, deduce_v2 and deduce_m2) can cause ODR issues in a case when e.g. third-party libraries depending on QVM specialized these traits differently and those libraries were used together. There were no consensus if this is indeed a library issue or how this issue could be handled in general. Taking into account that the specialization of these traits is optional it'd be sufficient to describe the issue in the documentation and discourage the users from specializing those traits for types defined outside of their own code. - There was also a suggestion to use the same names that are already being used in other well-known libraries to make the interface more intuitive, e.g. mag() could be replaced by norm() (used in Eigen and Armadillo libraries), mag2() could be replaced by norm_squared() or norm_sqr(), etc. This would also make the latter more verbose. I'd let the decission how to deal with it to Emil. - Another suggestion was to replace read/write semantics with get/set semantics or at least to make the r/w/ir/iw identifiers more verbose. Here, I'd let the decission how to deal with it to Emil as well. - Aside from the issues described above, there were also suggestions that the scope of QVM library could/should be broadened to include functionalities from domains other than computer graphics, e.g. linear algebra, geometry, physics, robotics, etc. Oswin Krause requested that an consensus on the scope of the library should be made before the acceptance of the library. Phil Endecott expressed that the library is too small to be a standalone library. However as a Boost.Geometry developer I may say that the scopes, design rationales, internal structures, etc. of both libraries are different. AFAIK it's also true for Boost.Polygon. Furthermore, if my understanding is correct after reading various discussions the community finds the library useful even in the current state, some of the participants already used the library in their projects. Furthermore I'm sure that future users of QVM will suggest additions to the QVM library if they think it's necessary, so the scope will be broadened in a natural way. Though of course I encourage Emil to start a discussion with the community regarding this issue. - Regarding the documentation, various people suggested the following improvements: * it should start with a "Quick Start" page showing how to use the QVM built-in types to do some high-school linear algebra, * make it more obvious which functions are classified as "operations" and which are "view proxies", * contain more examples of every function as well as some bigger real-life examples. Please let me know if you think something is wrong. Regards, Adam

3 4

Building Boost (1.60) with Clang and NDK
by Fatih Kıralioğlu 06 Jan '16

06 Jan '16

Has anyone built the Boost with Clang and NDK other than CryStax? If so, can you post the related config.jam and build script? I have handled gcc build but clang is very very chalnllenging and no one including the guys in Stackoverflow could answer it. Many Thanks. Fatih

4 3

[multiprecision] Creation from a range
by Fernando Pelliccioni 06 Jan '16

06 Jan '16

Hi John, hi all, Is there any way to create an Integer (or a number) from a range (bounded or counted)?; or from a string_view (string_ref)? Roughly speaking, something like: XintXXX_t make_from_bounded_range(I f, I l); XintXXX_t make_from_counted_range(I f, size_t n); If not exist, I can make a contribution, are you interested? Thank you very much and best regards, Fernando Pelliccioni.

3 3

[gsoc16] Re: Potential contribution scenarios?
by Miguel Coimbra 06 Jan '16

06 Jan '16

> It is not hard to find either myself or Antony. Both of us are here, > and both of us are at the top of Google search results for our names. Probably my bad, I only bumped into LinkedIn references. I'll wait for a reply from Antony as well, thanks. I will explore other ideas as well. > 1. A thing Boost really could do with is a decent (optionally > mmappable) dense hash map implementation, so the hash map could > contain billions of items and mostly reside on disk yet lookups would > still be very fast. I have some questions regarding this first idea. I believe a concept and implementation already exist and are actually in use at Google: http://goog-sparsehash.sourceforge.net/doc/dense_hash_map.html Quoting from that page: ** dense_hash_map is distinguished from other hash-map implementations by its speed and by the ability to save and restore contents to disk. On the other hand, this hash-map implementation can use significantly more space than other hash-map implementations, and it also has requirements -- for instance, for a distinguished "empty key" -- that may not be easy for all applications to satisfy. This class is appropriate for applications that need speedy access to relatively small "dictionaries" stored in memory, and for applications that need these dictionaries to be persistent." ** So what you want is something like this, but able to "contain billions of items and mostly reside on disk yet lookups would still be very fast"? I assume the "billions of items" is what is lacking from that dense_hash_map already in use by Google? Is this the difference between that and your idea? Assuming this is indeed what you were proposing, would the work encompass defining an API and also exploring mmap for lazy iteration for performance gains in the context of handling billions of items? Kind regards, Miguel E. Coimbra

2 1

Hi! Want to Contribute
by shubham tibra 06 Jan '16

06 Jan '16

Hello everone, I am Shubham Tibra, a student of IIT KHARAGPUR, INDIA and new to open source community. I can code in C, C++ and I would like to contribute in Boost C++ Libraries. Can someone help me in getting started? Thanks in advance.

2 1