Galvin,
that was reported when boost version 61 was used, and the application was compiled with g++ version 5.21 with options
CFLAGS += -fsanitize=alignment
CFLAGS += -fsanitize=object-size
CFLAGS += -fsanitize=vptr

Thanks,
David.


On Tuesday, August 16, 2016 7:39 AM, "boost-users-request@lists.boost.org" <boost-users-request@lists.boost.org> wrote:


Send Boost-users mailing list submissions to
    boost-users@lists.boost.org

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.boost.org/mailman/listinfo.cgi/boost-users
or, via email, send a message with subject or body 'help' to
    boost-users-request@lists.boost.org

You can reach the person managing the list at
    boost-users-owner@lists.boost.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Boost-users digest..."


Today's Topics:

  1. Re: some runtime errors in shared_count.hpp (Gavin Lambert)
  2. [boost][multiprecision] compile error with gcc 4.8.4 (Rob Conde)
  3. [property_tree] - unsuppressed warning under VS2015    Update 3
      (Tamas.Ruszkai@leica-geosystems.com)
  4. Re: [boost][multiprecision] compile error with gcc 4.8.4
      (John Maddock)
  5. Custom build of Python3 not picked up by Boost.Build
      (Matthieu Brucher)


----------------------------------------------------------------------

Message: 1
Date: Tue, 16 Aug 2016 11:21:20 +1200
From: Gavin Lambert <gavinl@compacsort.com>
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] some runtime errors in shared_count.hpp
Message-ID: <notipk$ak9$1@blaine.gmane.org>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 15/08/2016 23:04, David Frank wrote:
> boost/smart_ptr/detail/shared_count.hpp:484:41: runtime error: member
> call on address 0x0000055807b0 which does not point to an object of type
> 'sp_counted_base'
> 0x0000055807b0: note: object is of type
> 'boost::detail::sp_counted_impl_p<boost::detail::thread_data_base>'
>  00 00 00 00  10 82 bd b4 c1 7f 00 00  01 00 00 00 01 00 00 00  c0 29 5a
> 05 00 00 00 00  41 00 00 00
>              ^~~~~~~~~~~~~~~~~~~~~~~

Given that sp_counted_base is a base class of sp_counted_impl_p<>, I'm
inclined to think that whatever is reporting that is confused.

It's also useless to make a post like this without specifying what
version of Boost you are using and which tool is reporting these errors.




------------------------------

Message: 2
Date: Tue, 16 Aug 2016 00:59:24 +0000
From: Rob Conde <rob.conde@ai-solutions.com>
To: "boost-users@lists.boost.org" <boost-users@lists.boost.org>
Subject: [Boost-users] [boost][multiprecision] compile error with gcc
    4.8.4
Message-ID:
    <BN3PR0801MB23065F715AE0B9931115AE27C8130@BN3PR0801MB2306.namprd08.prod.outlook.com>
   
Content-Type: text/plain; charset="windows-1252"

Please see the scenario below...am I doing something wrong or is this a gcc or multiprecision bug?


Thanks,

Rob Conde



given the following code (multiPrecisionTest.cpp):


#include <boost/multiprecision/cpp_int.hpp>
#include <boost/multiprecision/cpp_bin_float.hpp>

typedef boost::multiprecision::int128_t int128_t;
typedef boost::multiprecision::cpp_bin_float_quad float128_t;

int main()
{
  int128_t intVal;
  float128_t floatVal(intVal.convert_to<float128_t>());

  return 0;
}


--------------------------------------------------------------------------

g++ -std=c++0x -c multiPrecisionTest.cpp


I get the following error:


In file included from ./boost/multiprecision/cpp_int.hpp:1936:0,
                from multiPrecisionTest.cpp:1:
./boost/multiprecision/cpp_int/misc.hpp: In instantiation of ?typename boost::enable_if_c<(boost::multiprecision::backends::is_trivial_cpp_int<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value && boost::multiprecision::is_signed_number<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value)>::type boost::multiprecision::backends::eval_convert_to(R*, const boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1>&) [with R = boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>; unsigned int MinBits1 = 128u; unsigned int MaxBits1 = 128u; boost::multiprecision::cpp_integer_type SignType1 = (boost::multiprecision::cpp_integer_type)1u; boost::multiprecis
ion::cpp_int_check_type Checked1 = (boost::multiprecision::cpp_int_check_type)0u; Allocator1 = void; typename boost::enable_if_c<(boost::multiprecision::backends::is_trivial_cpp_int<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value && boost::multiprecision::is_signed_number<boost::multiprecision::backends::cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1> >::value)>::type = void]?:
./boost/multiprecision/number.hpp:585:40:  required from ?void boost::multiprecision::number<Backend, ExpressionTemplates>::convert_to_imp(T*) const [with T = boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>; Backend = boost::multiprecision::backends::cpp_int_backend<128u, 128u, (boost::multiprecision::cpp_integer_type)1u, (boost::multiprecision::cpp_int_check_type)0u, void>; boost::multiprecision::expression_template_option ExpressionTemplates = (boost::multiprecision::expression_template_option)0u]?
./boost/multiprecision/number.hpp:601:29:  required from ?T boost::multiprecision::number<Backend, ExpressionTemplates>::convert_to() const [with T = boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>; Backend = boost::multiprecision::backends::cpp_int_backend<128u, 128u, (boost::multiprecision::cpp_integer_type)1u, (boost::multiprecision::cpp_int_check_type)0u, void>; boost::multiprecision::expression_template_option ExpressionTemplates = (boost::multiprecision::expression_template_option)0u]?
multiPrecisionTest.cpp:10:54:  required from here
./boost/multiprecision/cpp_int/misc.hpp:533:138: error: no type named ?type? in ?struct boost::common_type<boost::multiprecision::number<boost::multiprecision::backends::cpp_bin_float<113u, (boost::multiprecision::backends::digit_base_type)2u, void, short int, -16382, 16383>, (boost::multiprecision::expression_template_option)0u>, __int128 unsigned>?
    typedef typename common_type<R, typename cpp_int_backend<MinBits1, MaxBits1, SignType1, Checked1, Allocator1>::local_limb_type>::type common_type;
                                                                                                                                          ^

-------------- next part --------------
HTML attachment scrubbed and removed

------------------------------

[Message discarded by content filter]
------------------------------

Message: 4
Date: Tue, 16 Aug 2016 12:11:07 +0100
From: John Maddock <jz.maddock@googlemail.com>
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] [boost][multiprecision] compile error with
    gcc 4.8.4
Message-ID: <92c08c5d-6d9b-eea2-c8f6-2f337448f045@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed



On 16/08/2016 01:59, Rob Conde wrote:
> #include <boost/multiprecision/cpp_int.hpp>
> #include <boost/multiprecision/cpp_bin_float.hpp>
>
> typedef boost::multiprecision::int128_t int128_t;
> typedef boost::multiprecision::cpp_bin_float_quad float128_t;
>
> int main()
> {
>    int128_t intVal;
>    float128_t floatVal(intVal.convert_to<float128_t>());
>    return 0;
> }

That should work, as should:

float128_t f(intVal);

However, while both of these do work with msvc, they fail with GCC, so
there is a bug (or 2) somewhere.  I'll investigate later.

John.


------------------------------

Message: 5
Date: Tue, 16 Aug 2016 12:37:36 +0100
From: Matthieu Brucher <matthieu.brucher@gmail.com>
To: boost-users@lists.boost.org
Subject: [Boost-users] Custom build of Python3 not picked up by
    Boost.Build
Message-ID:
    <CAHCaCk+c0fF5=unwFp_nsr73gme48TRJLPCXyxt6VZD_os1zCA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

As I need a build of Python3 compatible with VS2012, I built it from
scratch and installed it in a _INSTALL folder, following a tutorial online.
Now, I want to use that Python3 with Boost.Python, so I did this in my
use-config.jam:
using python : 3.4 : D:/Tools/Python-3.4.5/_INSTALL/python.exe :
D:/Tools/Python-3.4.5/_INSTALL/include :
D:/Tools/Python-3.4.5/_INSTALL/libs ;

And then:

.\bootstrap.bat --with-python=D:\Tools\Python-3.4.5\_INSTALL
--with-python-version=3.4 --python-buildid=3
which failed.
The includes are found properly, but the link is floawed:

LINK : fatal error LNK1104: cannot open file 'python34.lib'

The library is in D:/Tools/Python-3.4.5/_INSTALL/libs, but could not be
found according to the log.
Also, something strange:
D:\Tools\boost_1_60_0\tools\build\src\engine>.\bootstrap\jam0 -f build.jam
--toolset=vc14 "--toolset-root=C:\Program Files (x86)\Microsoft Visual
Studio 14.0\Common7\Tools\..\..\VC\ "
--with-python=D:\Tools\Python-3.4.5\_INSTALL --with-python-version=3.4
--python-buildid=3

The retrieved toolset is wrong, as explicitely asked for VS2012 aka 11.0
int he user-config.jam and I'm running it from a VS2012 x64 native tools
command prompt.

Couldn't find any help online, so the best is to ask the Boost community!

Regards,

Matthieu
--
Information System Engineer, Ph.D.
Blog: http://blog.audio-tk.com/
LinkedIn: http://www.linkedin.com/in/matthieubrucher
-------------- next part --------------
HTML attachment scrubbed and removed

------------------------------

Subject: Digest Footer

_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users

------------------------------

End of Boost-users Digest, Vol 4538, Issue 1
********************************************