- Boost - lists.preview.boost.org

[qvm] Review announcement
by Phil Endecott 09 Dec '15

09 Dec '15

Adam Wulkiewicz wrote: > The formal review of Emil Dotchevski's QVM library begins > today on 7th Dec and ends on 16th Dec. Adam sent this announcement email to the boost@, boost-users@ and boost-announce(a)lists.boost.org lists. Which seems OK, except that as I have previously noted the gmane.org website seems to get confused by such messages; this announcement will have appeared on only the announce page at gmane.org and any followups that are sent to e.g. the boost@ list will not be displayed by gmane at all. You might argue that this is a gmane.org bug, and that is true, but on the other hand we do want everyone who might be interested to know about the review, and a quick look at email headers will show that many do use the gmane.org web interface to read these lists. I've previously suggested that whatever "how to be a review manager" documentation that exists should advise that announcements should be posted separately to each list. Perhaps no such documentation exists! (I'll post some comments about the actual proposal soon.) Regards, Phil.

2 1

[LOG] formatting_ostream API change
by Andrew Hundt 09 Dec '15

09 Dec '15

I had the following code, which worked in 1.58: #include <boost/log/trivial.hpp> #include <boost/exception/all.hpp> #include <boost/algorithm/string.hpp> /// @todo move elsewhere, because it will conflict with others' implementations of outputting vectors template<typename T> inline boost::log::formatting_ostream& operator<<(boost::log:: formatting_ostream& out, std::vector<T>& v) { out << "["; size_t last = v.size() - 1; for(size_t i = 0; i < v.size(); ++i) { out << v[i]; if (i != last) out << ", "; } out << "]"; return out; } I used it to output a std::vector<float> as follows: BOOST_LOG_TRIVIAL(trace) << “Real joint angles from FRI: " << realJointPosition << "\n"; However this now seems to fail in 1.59. I’ve created a github gist with the compiler output <https://gist.github.com/ahundt/5869dbd09e889b7153c3> in case that’s helpful as well. I see that the update recently had some breaking changes, what is the new way to provide the desired functionality? Thanks for your help. Cheers! Andrew Hundt

2 3

Boost release 1.60.0 beta 1 is now available from SourceForge
by Marshall Clow 08 Dec '15

08 Dec '15

Boost release 1.60.0 beta 1 is now available from SourceForge. See http://sourceforge.net/projects/boost/files/boost/1.60.0.beta.1/ For details of what's in the release, see http://www.boost.org/users/history/version_1_60_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Known issues: * Errors when building Boost.TypeErasure for older versions of Visual Studio. * Boost.Test fails when building on Darwin with gcc 4.9.2 The files (and associated md5s) are: MD5 (boost_1_60_0_b1.7z) = 63530c9594b24f56e5df79d910c9daeb MD5 (boost_1_60_0_b1.tar.bz2) = 29af12a1028536219a21517e953df4eb MD5 (boost_1_60_0_b1.tar.gz) = 74df7f5eb5e32f3a92b6141af3c6f541 MD5 (boost_1_60_0_b1.zip) = 90c25c34b64eb6cc88845ec5372938d7 Thanks, -- The Boost Release Team

2 1

Checking for #pragma GCC diagnostic push|pop availability
by Marshall Clow 08 Dec '15

08 Dec '15

Shane Turner wrote: > I found another issue with a bad compiler version check in > boost/interprocess/detail/config_begin.hpp before using "#pragma GCC > diagnostic push", which, for GCC, is only available at version 4.6.0 and > later. Since I'm using GCC 4.4.7, my compile fails. It looks to me like interprocess is the one that really needs fixing. [ There could be a lot of cleanup here, but that's for another time ] I will make a PR. -- Marshall I have found (in non-test code) #if defined(__GNUC__) && (__GNUC__*10000 + __GNUC_MINOR__*100 + __GNUC_PATCHLEVEL__ > 40800) type_traits/has_logical_not.hpp #if BOOST_GCC >= 40700 tuple/detail/tuple_basic.hpp #Effectively >= 40600 smart_ptr/shared_ptr.hpp smart_ptr/scoped_ptr.hpp smart_ptr/detail/shared_count.hpp #if defined(BOOST_GCC) && BOOST_GCC >= 40600 random/detail/disable_warnings.hpp random/detail/enable_warnings.hpp #if defined(__clang__) move/detail/std_ns_begin.hpp move/detail/std_ns_end.hpp #elif defined(__GNUC__) && !(defined(__INTEL_COMPILER) || defined(__ICL) || defined(__ICC) || defined(__ECC)) \ && (__GNUC__ * 100 + __GNUC_MINOR__) >= 406 log/detail/header.hpp log/detail/footer.hpp #if defined(__clang__) || (defined(__GNUC__) && !(defined(__INTEL_COMPILER) || defined(__ICL) || defined(__ICC) || defined(__ECC)) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 6))) lexical_cast/try_lexical_convert.hpp #if defined(BOOST_GCC) && (BOOST_GCC >= 40000) interprocess/detail/config_begin.hpp interprocess/detail/config_end.hpp #Effectively >= 40600 get_pointer.hpp

2 1

[boost-users][boost-announce][QVM] Formal review begins today
by Adam Wulkiewicz 07 Dec '15

07 Dec '15

Dear Boost community, The formal review of Emil Dotchevski's QVM library begins today on 7th Dec and ends on 16th Dec. Boost QVM defines a set of generic functions and operator overloads for working with quaternions, vectors and matrices of static size with the emphasis on 2, 3 and 4-dimensional operations needed in graphics, video games and simulation applications. While it provides its own quaternion, matrix and vector types, it is designed to work primarily with user-defined types through user specializations of the q_traits, v_traits and m_traits templates. QVM's source code is available on Github: https://github.com/zajo/boost-qvm Full documentation is also viewable on Github: http://zajo.github.io/boost-qvm/ We encourage your participation in this review. At a minimum, kindly state: - Whether you believe the library should be accepted into Boost * Conditions for acceptance - Your name - Your knowledge of the problem domain. You are strongly encouraged to also provide additional information: - What is your evaluation of the library's: * Design * Implementation * Documentation * Tests * Usefulness - Did you attempt to use the library? If so: * Which compiler(s) * What was the experience? Any problems? - How much effort did you put into your evaluation of the review? More information about the review process can be found here: http://www.boost.org/community/reviews.html We await your feedback! Best regards, Adam Wulkiewicz

1 0

interest in an asynchronous linear algebra library?
by Oswin Krause 07 Dec '15

07 Dec '15

Hi list, Disclaimer: What I am proposing here does not exist (yet). But it will in the near future and if there is interest i would like to give something back to the boost community. I would like to propose a new library to boost: asynchronous blas. What is it and what can I do with it? It is a linear algebra library where all computations are carried out in an asynchronous manner on GPU and CPU. Computing a matrix-matrix product does not block the current thread but instead launches a task which at some point returns with a result, allowing the main thread to continue until the result is needed. GPU and CPU tasks can be started at the same time depending on each other (e.g. a CPU computation waits until the GPU returned some needed result and vice-versa) Why is this important? Which problems does it solve? Many linear algebra libraries are target towards either a) solving a few large linear algebra problems b) solving many small similar problems This library is targeted towards the middle ground: a medium amount of decently sized problems. Here the problem is that it is often hard to use all the computing resources available as a single problem will not exhaust the device resources and there is no easy way to launch several similar tasks in parallel. This problem occurs often in GPU computing where out-of-order execution of kernels is used to fill up the device. Similarly, it is often hard to make CPU and GPU work together as GPU tasks are asynchronous while CPU tasks are often synchronous and it is not straight forward to couple both without blocking either CPU or GPU. How does it work? Expression templates similar to boost::ublas are used to create a dependency graph: which object is used in which computations and which tasks have to wait to ensure a correct outcome? a simple case would be two independent computations like matrix A=prod(B,trans(B)); matrix C=prod(trans(B),B); a normal library like ublas would wait until A is computed before C is evaluated. Instead, it can be more efficient to just add the two tasks to a list and let worker threads execute them as soon as resources are available. First the computation of A is put into the graph and A is marked as "being written to" while B is marked as "being read". When C is added to the list, it does not depend on the first computation as several tasks can read from B at the same time. So another worker thread can grab the task and execute it. If we now add the task B += prod(D,prod(C,trans(D)); the library computes it as matrix temp = prod(C,trans(D); B += prod(D,temp). temp can be computed as soon as C is computed. But B can only be computed after A and temp are computed as we can only write to B after all previous tasks using B are finished. Are you qualified? I am main contributor to https://github.com/Shark-ML/Shark/ and as part of it I forked ublas https://github.com/Shark-ML/Shark/tree/master/include/shark/LinAlg/BLAS which now uses several linear algebra libraries as possible backends (ATLAS, openBLAS...). What is the timeline? I would start developing a minimal example ASAP based on the rewrite of ublas above. I would use a minimum set of features (only dense square matrices) and basic GPU support. Opinions? Best, Oswin

8 17

[asio] Any interest in a boost::asio::mockup_serial_port ?
by Damien Buhl 07 Dec '15

07 Dec '15

Dear Boost.Asio developers, I wanted to know if there was any interest for a mockup_serial_port_service, so that one might write cross platform unit-tests of code based on serial_port. I implemented this mockup this summer for a project where the best way to unit test some modules was to act as another peer on a serial port and needed to be doable on any platform supported by asio::serial_port. I find it quite useful, because there - is no need to use separate tools like socat on linux or install virtual COM ports applications on windows. Which ease the setup of the test environment - the fake serial port doesn't pollute the system where the test is run - many test cases can be run in parallel, as there is no native ressources involved. One might use it as this : > using namespace boost::asio; > > boost::thread simulate_writing_device([](){ > io_service ios; > basic_serial_port<mockup_serial_port_service> port{ios, "my_fake_serial_port"}; > > const std::string message = "Hello"; > > for (;;) { > boost::asio::write(port, buffer(message.data(), message.size())); > boost::this_thread::sleep_for(boost::chrono::seconds(1)); > } > > }); > > boost::thread simulate_reading_device([](){ > io_service ios; > basic_serial_port<mockup_serial_port_service> port{ios, "my_fake_serial_port"}; > > for (;;) { > char message[5]; > boost::asio::read(port, buffer(message, 5)); > std::cout << "received : " << std::string(message, 5) << std::endl; > } > > }); A short documentation is available here : http://goo.gl/24JnUg And the implementation is on github in a holdall library for the moment : https://goo.gl/E7KGdn It's a library whose goal is to shrink over the time as they get merged in upstreams project. Hopefully there is interest for this mockup_serial_port, and if so I'll cleanup the code some more and make a pull-request to Boost.Asio. Cheers from Berlin where meetingcpp already ended :'-( -- Damien Buhl

2 2

[fiber] ready for next review
by Oliver Kowalke 06 Dec '15

06 Dec '15

As request, I'd like to announce that boost.fiber has addressed the requests of the last review. Especially migrating fibers between threads is supported - sub-directory 'examples' contains code demonstrating work-sharing and work-stealing. boost.fiber: github.com/olk/boost-fiber/tree/develop (branch develop) requires boost.context (branch develop) Oliver

2 22

Boost 1.60.0 beta 1 Release Candidate 2 available for testing
by Marshall Clow 04 Dec '15

04 Dec '15

Release candidate files for 1.60.0 beta 1 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. Changes since rc1: * Boost.Sprit has been updated and Boost.Log now builds. * Boost.Math has been updated and now builds. Known issues: * Errors when building libraries for visual studio: test and type_erasure. * Boost.Test fails when building on Darwin with gcc 4.9.2 The files (and associated md5s) are: MD5 (boost_1_60_0_b1_rc2.7z) = dd38daa9378a6002fc12da0cab695511 MD5 (boost_1_60_0_b1_rc2.tar.bz2) = f3c9ffc14db3b2e55c7c5c703e69883d MD5 (boost_1_60_0_b1_rc2.tar.gz) = 89365262443cc16990b69f8e4b8b47ab MD5 (boost_1_60_0_b1_rc2.zip) = 3389bd4595a989fe95966440cbe45ca9 Thanks! -- The release managers

7 12

thread_specific crashes the application when it is in a .so file
by George Georgiev 03 Dec '15

03 Dec '15

Hi, Is there a known issue about boost::thread_specific when a global thread_specific object is in a .so file? The exact same code replacing it with thread_local boost::unique_ptr<Foo> works. By the way is there a macro that determines is thread_local supported from the compiler or not? Thanks, George

3 3

Documentation for boostbook
by Soul Studios 02 Dec '15

02 Dec '15

I've seen the existing documentation, and wasn't impressed- is there a better site for details on this? Something with at minimum, a copy of the DTD and an example .xml file? Thanks, Matt

1 0

compilation errors with ublas / cppad
by Peter Caspers 30 Nov '15

30 Nov '15

Hi, I think this has been asked before, but since I am not aware of any answer, I would like to bring up the topic again: When using CppAD::AD<double> with boost ublas, certain compilation errors show up. I attach a small example (ublas_cppad.cpp) and the (start of the) error messages I get (compilation_errors.txt, produced with boost 1.59.0, g++ 4.9.3, CppAD-20151124). The problem is in matrix_assign.hpp; when changing template<class E1, class E2, class S> BOOST_UBLAS_INLINE bool equals (const matrix_expression<E1> &e1, const matrix_expression<E2> &e2, S epsilon, S min_norm) { return norm_inf (e1 - e2) < epsilon * std::max<S> (std::max<S> (norm_inf (e1), norm_inf (e2)), min_norm); } to template<class E1, class E2, class S> BOOST_UBLAS_INLINE bool equals (const matrix_expression<E1> &e1, const matrix_expression<E2> &e2, S epsilon, S min_norm) { S tmp = norm_inf (e1 - e2); return tmp < epsilon * std::max<S> (std::max<S> (norm_inf (e1), norm_inf (e2)), min_norm); } the example code compiles without errors. Can someone point out, how this should be fixed (either on boost or CppAD side)? In general, are there requirements for a type T to cooperate with ublas matrices one should be aware of? Thank you Peter

2 3

Is master branch open for bug fixes?
by Vicente J. Botet Escriba 30 Nov '15

30 Nov '15

Hi, the calendar says that master branch is open for bug fixes, but not mail has been sent to to notify it. Could some release manager confirm that? Best, Vicente

2 2

[program_options] empty string argument
by Benedek Thaler 30 Nov '15

30 Nov '15

Hi, I have the exact same problem: http://boost.2283326.n4.nabble.com/ProgramOptions-explicit-empty-string-arg… --compression '' gave me a specified, empty compression switch value, as expected, on boost 1.58. However, on 1.59, the empty string counts against the positional arguments, and causes regressions. Also, --compression='' gives: The argument for option '--compression' should follow immediately after the equal sign. What is the recommended workaround? Is it planned to be fixed/changed? Thanks, Benedek

1 0

[Boost.LLVM] Synopsis now available
by Andy Jost 29 Nov '15

29 Nov '15

I've created a new GitHub repository for this project and uploaded a synopsis of the proposed interface. I redesigned the interface, so it differs slightly from the prototype code and examples I gave before. Please take a look and provide feedback if you can! https://github.com/andyjost/Boost.LLVM/blob/master/boost_llvm.cpp -Andy

1 0

Interest in an LLVM library?
by Andy Jost 26 Nov '15

26 Nov '15

Is there interest in an LLVM library? My motivation is to simplify the dynamic creation of functions, modules, and programs by defining an EDSL modeled after the C language. LLVM provides an API based exclusively on function calls that is verbose and difficult to use. The EDSL is more expressive and easier to use. (This may remind some people of Boost.Python and indeed these libraries are similar in motivation.) The scope of this proposal is limited. The proposed library does not compile, link, optimize, save, or load anything, for example, since the LLVM API is suitable for that. Also, it may not support obscure features, even if they seem to be within its purview, since one can always make direct calls to the LLVM API. I have written about 6500 lines of prototype code in the context of another project (a compiler for the language Curry, if anyone is interested). It is not a complete solution, but is by no means trivial, either. I'll discuss that next, but since the discussion is somewhat lengthy, let me first explain what I'm looking for by sending this. I think this EDSL would make a good Boost library. If others agree, then the next step is to review the design. I need second opinions and help from more knowledgeable people to improve the design. There are a few places in particular where I think a redesign is necessary. After that, I'm happy to implement the final library (and would gladly accept help, if anyone is interested). Now, I'll show a few examples and provide links to the prototype code. First, here's how to create a module and put it in scope: module const example_module("example"); scope _ = example_module; The scope object sets the insertion point for types, functions, and global variables. We can create a type as follows: type i32 = int_(32); i32 is a 32-bit integer. It is easy to build more complex types, e.g., i32[2] is an array type, *i32 is a pointer type, and i32(i32,i32) is a function type. An expression like i32(42) produces a constexpr. As you might guess at this point, the prototype makes heavy use of SFINAE. I've gone to a lot of effort to make this work with everything I can think of, particularly multi-dimensional arrays and initializer_lists. So, an expression like (i32[3][2])({{1,2,3},{4,5,6}}) works! (Note: i32[3][2] is the C++ type int32_t[2][3] because that's the only sensible way to interpret successive calls to operator[]). We can create a struct from a sequence of types like this: type foo = struct_("foo", {i32, *i32}); Or, we can leave out the sequence to get an opaque struct. A function prototype can be created as follows: function const f = extern_(i32(i32), "f", {"i"}); This function, f, takes an i32 (named "i") and returns an i32. The function is placed in example_module, since the code appears in its scope. There are two other linkage-specifying functions: static_ and inline_. extern_ and static_ are also used to create global variables (i.e., if the type is not a function). To define the body, we create another scope: { scope _ = f; // code for f. } To understand this, we have to discuss scopes in more depth. There are three nested levels of scope: the current module, the current function, and the current basic block. The code above sets the current function to f and the current basic block to f's entry point. Generally speaking, within a function body we write statements that generate instructions. Those instructions are inserted into the current function at the end of the current basic block. To define the body, we can declare values and operate on them. For example: value i = arg("i"); Here, "arg" is a special function that fetches the named function parameter. We can add instructions to f using operators or special methods. For example: value j = i + 1; return_(j); Branches manipulate the current basic block. Here's an if statement: label true_path, false_path; if_(i, true_path, false_path); { scope _ = true_path; // code for true. } /* else */ { scope _ = false_path; // code for false. } // new basic block here. This generates instructions to test i, take the appropriate branch, and then continue to a new basic block in the right places (which depends on whether the paths terminate with a branch instruction). It also updates the scope so that statements following if_() are inserted into the new basic block. Believe me when I say it is not trivial to do this with the LLVM API. Although it is sometimes necessary to pre-declare labels as shown above, we can usually employ C++11 lambdas to simplify the encoding: if_(i , []{ /* code for true */} , []{ /* code for false */ } ); The prototype code can be found under https://github.com/andyjost/Sprite-3/tree/master/include/sprite/backend. Also, there are many examples under https://github.com/andyjost/Sprite-3/tree/master/examples. Other parts of the Sprite-3 project are unrelated to this proposal. A good example to start with generates the Fibonacci numbers (https://github.com/andyjost/Sprite-3/blob/master/examples/fib.cpp) Here's the interesting part: // Create a new module and associate it with this lexical scope. module const fib_module("fib"); scope _ = fib_module; // Declare types. auto const char_ = types::char_(); auto const i32 = types::int_(32); auto const i64 = types::int_(64); // Declare external functions. auto const printf = extern_(i32(*char_, dots), "printf"); // Define the @fib function. auto const fib = extern_(i64(i64), "fib", {"n"}); { scope _ = fib; value n = arg("n"); if_(n <(signed_) (2), []{return_(1);}); return_(fib(n-2) + fib(n-1)); } // Define the @main function. auto const main = extern_(i32(), "main"); { scope _ = main; value const x = fib(5); printf("fib(5)=%d\n", x); return_(0); } After this code runs, fib_module contains an intermediate representation of the program. The LLVM API can be used to save that to disk, compile it to assembly, link in the C library (to get printf), or JIT compile any of the functions, among other things. Thanks to everyone who made it this far :) I'm looking forward to your feedback. -Andy

9 21

[trippels-ppc64le][math] Missing quadmath.h errors
by Andrey Semashev 24 Nov '15

24 Nov '15

Hi, I'm seeing some test failures on the trippels-powerpc64le-gcc-6.0 tester that amount to Boost.Math failing to build because the quadmath.h header is missing. http://www.boost.org/development/tests/develop/developer/output/trippels-po… I understand that gcc 6.0 is an unreleased compiler, but the error is probably not a consequence of a compiler bug. Besides, another tester, Flast-FreeBSD10-gcc-6.0.0~gnu++11, passes. Is it possible that the header is not provided for powerpc64le? Or is an optional dependency whose presence is misdetected? Is this a known problem?

3 5

[teeks99][test] Test failures on MSVC 8-11
by Andrey Semashev 23 Nov '15

23 Nov '15

Hi, I'm seeing massive Boost.Log test failures on teeks99 with MSVC versions 8 through 11. The links to the failure messages lead to Boost.Test but the console output is not helpful (shows a successful compilation of a source file [1]). I can see Boost.Test tests are also failing massively on these compilers. Could this be fixed? [1]: http://www.boost.org/development/tests/develop/developer/output/ teeks99-08d-win2012R2-64on64-boost-bin-v2-libs-log-test-attr_attribute_set- test-msvc-11-0-dbg-adrs-mdl-64-thrd-mlt.html

6 18

[Config] boost::uint32_t != std::uint32_t on some targets
by Louis Dionne 23 Nov '15

23 Nov '15

Dear Boost, I recently fell into a trap where a program wouldn't compile because of a difference between `boost::uint32_t` and `std::uint32_t`. Specifically, I was trying to cross-compile from OS X to ARM, and the following program wouldn't compile #include <boost/cstdint.hpp> #include <cstdint> #include <type_traits> static_assert(std::is_same<std::uint32_t, boost::uint32_t>::value, ""); int main() { } I was building with arm-none-eabi-g++ -I /path/to/boost -std=c++11 -c main.cpp I have asked a question on StackOverflow [1], and I now understand why the two types are not required to be the same. However, I think it is a QOI issue that those two types are not the same, since it makes interoperating between `std::uint32_t` and `boost::uin32_t` more difficult. Is there a reason for this difference, and if not would it be reasonable to ensure that `boost::uint32_t == std::uint32_t` whenever the latter is defined, i.e. in C++11 and above? Regards, Louis [1]: http://stackoverflow.com/q/33857554/627587

3 2

build and install boost subset does not install the header files
by George Georgiev 22 Nov '15

22 Nov '15

Hi, I am trying to use github boost to obtain a subset of the libraries. I found that using the following subset of modules allows me to build boost_system. git submodule update --init tools/build || exit 1 git submodule update --init tools/inspect || exit 1 git submodule update --init libs/assert || exit 1 git submodule update --init libs/config || exit 1 git submodule update --init libs/core || exit 1 git submodule update --init libs/predef || exit 1 git submodule update --init libs/system || exit 1 git submodule update --init libs/utility || exit 1 The problem is that ./b2 ... install does not copy the header files. Is this a bug that I am hitting? My commands are: ./bootstrap.sh --prefix=../../boost --includedir=../../boost/include || exit 1 PATH=$CLANGBIN:$PATH \ ./b2 \ toolset=clang \ cxxflags="-std=c++11 -stdlib=libc++ -isystem/Developer/SDKs/MacOSX10.7.sdk/usr/include" \ linkflags="-stdlib=libc++" \ install threading=multi link=static Thanks, -g

2 3

[type_traits] Is_nothrow_move_constructible fails on mngw
by Andrzej Krzemienski 21 Nov '15

21 Nov '15

Hi, It looks like is_nothrow_move_constructible (in branch develop, on testers igaztanaga-gcc-4.6c++11 and igaztanaga-gcc-4.7c++11) fails the compilation rather than returning a true-false answer. <http://www.boost.org/development/tests/develop/igaztanaga-gcc-4-7c++11.html>I filed a ticket for it: https://svn.boost.org/trac/boost/ticket/11811 Reards, &rzej

1 0

[thread] Boost threading on VMware ESXi
by Fu ji 20 Nov '15

20 Nov '15

Hello, Is there anyone who try to use boost threading on ESXi (posix like system from VMware) or try to port it? Best regards, Damian

1 0

Re: [boost] boost log memory leak? Maybe it is my wrong.
by Jefferyliangmh 16 Nov '15

16 Nov '15

Many thanks andrey.semashev's reply. I send my demo application codes in BoostDemo.rar file. "logger" is my wrapped module by win32 dll. "BoostDemo" is my MFC test application, call logger code written in CMainFrame::CMainFrame() fuction, like this : AppLogger::log("this is test message"). Memory leak display in output windows when compiled BoostDemo application. 2015-11-16 2015-11-16 Jefferyliangmh 发件人：boost-request(a)lists.boost.org 发送时间：2015-11-16 01:00 主题：Boost Digest, Vol 4908, Issue 1 收件人："boost"<boost(a)lists.boost.org> 抄送： Send Boost mailing list submissions to boost(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.boost.org/mailman/listinfo.cgi/boost or, via email, send a message with subject or body 'help' to boost-request(a)lists.boost.org You can reach the person managing the list at boost-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost digest..." The boost archives may be found at: http://lists.boost.org/Archives/boost/ Today's Topics: 1. boost log memory leak? Maybe it is my wrong. (=?UTF-8?B?5qKB5piO6L6J?=) 2. Re: boost log memory leak? Maybe it is my wrong. (Andrey Semashev) 3. Re: checking __INTEL_COMPILER == 9999 (Blower, Melanie) 4. Re: checking __INTEL_COMPILER == 9999 (Edward Diener) ---------------------------------------------------------------------- Message: 1 Date: Sat, 14 Nov 2015 19:31:28 +0800 From: "=?UTF-8?B?5qKB5piO6L6J?="<liang_mh(a)163.com> To: "boost"<boost(a)lists.boost.org> Subject: [boost] boost log memory leak? Maybe it is my wrong. Message-ID: <220730f2.126658.15105c3ab0c.Coremail.liang_mh(a)163.com> Content-Type: text/plain; charset="UTF-8" Way I want to use win32 dynamic link library encapsulates the boost.log, the wrapper DLL in MFC MSVC 2015 calls, memory leak in output window prompt; The same library in a console program calls, no such problems. I am very depressed. Who can help me? 2015-11-14 ??? ------------------------------ Message: 2 Date: Sun, 15 Nov 2015 00:05:28 +0300 From: Andrey Semashev <andrey.semashev(a)gmail.com> To: "boost(a)lists.boost.org" <boost(a)lists.boost.org> Subject: Re: [boost] boost log memory leak? Maybe it is my wrong. Message-ID: <CAEhD+6BH=Lnw1ghLwOVarXbYGDBqoNygzcWnML+TtU7mVbB1zQ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Sat, Nov 14, 2015 at 2:31 PM, ??? <liang_mh(a)163.com> wrote: > Way I want to use win32 dynamic link library encapsulates the boost.log, the wrapper DLL in MFC MSVC 2015 calls, memory leak in output window prompt; The same library in a console program calls, no such problems. > I am very depressed. Who can help me? If you work with Boost.Log the same way in both cases then it's likely a problem in your code and not the library. Otherwise I can't help without a minimal working code sample. ------------------------------ Message: 3 Date: Sun, 15 Nov 2015 13:05:27 +0000 From: "Blower, Melanie" <melanie.blower(a)intel.com> To: "boost(a)lists.boost.org" <boost(a)lists.boost.org> Subject: Re: [boost] checking __INTEL_COMPILER == 9999 Message-ID: <B3584E72CFEBED439A3ECA9BCE67A4EF40258FCC(a)fmsmsx116.amr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" Thanks for all your suggestions and replies, I will work it on the Intel side. To Edward, at the bottom of my first message there's info about one of the failure modes. --Melanie ------------------------------ Message: 4 Date: Sun, 15 Nov 2015 10:43:25 -0500 From: Edward Diener <eldiener(a)tropicsoft.com> To: boost(a)lists.boost.org Subject: Re: [boost] checking __INTEL_COMPILER == 9999 Message-ID: <n2a971$msb$1(a)ger.gmane.org> Content-Type: text/plain; charset=windows-1252; format=flowed On 11/15/2015 8:05 AM, Blower, Melanie wrote: > Thanks for all your suggestions and replies, I will work it on the Intel side. To Edward, at the bottom of my first message there's info about one of the failure modes. Thanks, I see that now. ------------------------------ Subject: Digest Footer _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ------------------------------ End of Boost Digest, Vol 4908, Issue 1 **************************************

1 0

checking __INTEL_COMPILER == 9999
by Blower, Melanie 15 Nov '15

15 Nov '15

A few years ago, circa 2010, the Intel 12.x compiler was released without having a correct value for the macro __INTEL_COMPILER. It was released using the development-only version number 9999 instead of the correct value 12xx. Later on, an Intel 12.x compiler was updated to remove this problem and the version number made correct. Meanwhile, since boost needed to add some workarounds, there was code added in a couple of boost files to check for version 9999. The check for 9999 in boost causes trouble in our current development compiler in-house testing. Is it possible to have this version checking removed from the boost sources? There's no advantage to boost users, and possibly a disadvantage if someone is still using a not-updated 12.x compiler. But hopefully that is unlikely, we're currently shipping our 16.x compiler. Here's the diff, diff --git a/include/boost/config/compiler/intel.hpp b/include/boost/config/compiler/intel.hpp index 7789b94..bbbf876 100644 --- a/include/boost/config/compiler/intel.hpp +++ b/include/boost/config/compiler/intel.hpp @@ -47,11 +47,7 @@ #undef BOOST_COMPILER #if defined(__INTEL_COMPILER) -#if __INTEL_COMPILER == 9999 -# define BOOST_INTEL_CXX_VERSION 1200 // Intel bug in 12.1. -#else # define BOOST_INTEL_CXX_VERSION __INTEL_COMPILER -#endif #elif defined(__ICL) # define BOOST_INTEL_CXX_VERSION __ICL #elif defined(__ICC) @@ -93,11 +89,7 @@ #include "boost/config/compiler/common_edg.hpp" #if defined(__INTEL_COMPILER) -#if __INTEL_COMPILER == 9999 -# define BOOST_INTEL_CXX_VERSION 1200 // Intel bug in 12.1. -#else # define BOOST_INTEL_CXX_VERSION __INTEL_COMPILER -#endif #elif defined(__ICL) # define BOOST_INTEL_CXX_VERSION __ICL #elif defined(__ICC) @@ -289,7 +281,7 @@ template<> struct assert_intrinsic_wchar_t<unsigned short> {}; // (Niels Dekker, LKEB, May 2010) // Apparently Intel 12.1 (compiler version number 9999 !!) has the same issue (compiler regression). #if defined(__INTEL_COMPILER) -# if (__INTEL_COMPILER <= 1110) || (__INTEL_COMPILER == 9999) || (defined(_WIN32) && (__INTEL_COMPILER < 1600)) +# if (__INTEL_COMPILER <= 1110) || (__INTEL_COMPILER == 1210) || (defined(_WIN32) && (__INTEL_COMPILER < 1600)) # define BOOST_NO_COMPLETE_VALUE_INITIALIZATION # endif #endif Here's the other checking for 9999 that I found. Not known to cause a problem. diff --git a/include/boost/regex/v4/regex_format.hpp b/include/boost/regex/v4/regex_format.hpp index e9006a7..bf2e552 100644 --- a/include/boost/regex/v4/regex_format.hpp +++ b/include/boost/regex/v4/regex_format.hpp @@ -180,7 +180,7 @@ private: } inline int toi(ForwardIter& i, ForwardIter j, int base) { -#if defined(_MSC_VER) && defined(__INTEL_COMPILER) && ((__INTEL_COMPILER == 9999) || (__INTEL_COMPILER == 1210)) +#if defined(_MSC_VER) && defined(__INTEL_COMPILER) && (__INTEL_COMPILER == 1210) // Workaround for Intel support issue #656654. // See also https://svn.boost.org/trac/boost/ticket/6359 return toi(i, j, base, mpl::false_()); The intel.hpp check for 9999 causes this problem, among others, float128 tests from (boost_multiprecision suite) fail due to workaround in intel.hpp fo 12.1 compiler that was released with __INTEL_COMPILER == 9999 Fails like this: $ "icpc" -c -xc++ -O0 -w1 -inline-level=0 -fPIC -m64 -DBOOST_ALL_NO_LIB=1 -DSLOW_COMPILER -DTEST_FLOAT128 -I"../../.." -I"../include" -c -o "../../../bin.v2/libs/multiprecision/test/test_tanh_float128.test/intl-lnx/dbg/dbg-symbl-\ off/test_tanh.o" "test_tanh.cpp" In file included from test_tanh.cpp(53): ../../../boost/multiprecision/float128.hpp(48): error: identifier "_Quad" is undefined typedef _Quad float128_type; ^ Thanks and regards, Melanie Blower

5 6

boost log memory leak? Maybe it is my wrong.
by 梁明辉 14 Nov '15

14 Nov '15

Way I want to use win32 dynamic link library encapsulates the boost.log, the wrapper DLL in MFC MSVC 2015 calls, memory leak in output window prompt; The same library in a console program calls, no such problems. I am very depressed. Who can help me? 2015-11-14 梁明辉

2 1