Subject: Re: [boost] Libraries and C++ compliance
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2017-04-11 12:37:45
On 11/04/2017 08:03, Olaf van der Spek 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?
What did the statement say?
"Outcome is a header only C++ 14 library known to work on these
compilers or better:
clang 3.5 (LLVM)
clang 3.7 (with Microsoft Codegen)
VS2015 Update 2
I cannot help if you don't read the text.
>> VS2017 which implements C++ 14
>> constexpr and has a better optimiser for modern C++, you will see tigher
> This bit makes it sound VS2017 is required to avoid the code bloat.
Exactly what the statement says. I don't see why we are discussing this?
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/