Re: [boost] Libraries and C++ compliance

Subject: Re: [boost] Libraries and C++ compliance
From: Olaf van der Spek (ml_at_[hidden])
Date: 2017-04-11 07:03:40

On Mon, Apr 10, 2017 at 3:20 PM, Niall Douglas via Boost
<boost_at_[hidden]> wrote:
> On 10/04/2017 10:09, Olaf van der Spek wrote:
>> On Mon, Apr 10, 2017 at 9:04 AM, Niall Douglas via Boost
>> <boost_at_[hidden]> wrote:
>>> Warning: MSVC generates significant code bloat when using Outcome in
>>> large code bases. If you can use VS2017 which implements C++ 14
>>> constexpr and has a better optimiser for modern C++, you will see tigher
>>> executables. Execution speed is not particularly different, though one
>>> would have thought the extra cache load caused by code bloat might
>>> affect some applications. In this situation, use LLVM clang targeting
>>
>> What situation? VS2015?
>>
>>> the MSVC ABI."
>
> Note the phrase "Warning: **MSVC** generates significant ..."
>
> Note the earlier mention that VS2015 Update 2 or later is known to work.
> This implies VS2015 Update 1 or earlier does not.

Does it not work at all or does it do bloated code?

> VS2017 which implements C++ 14
> constexpr and has a better optimiser for modern C++, you will see tigher
> executables.

This bit makes it sound VS2017 is required to avoid the code bloat.

-- 
Olaf