Re: [boost] [review] outcome broken on clang/libstdc++ (Linux) and Apple clang/libc++ and gcc 7.2

Subject: Re: [boost] [review] outcome broken on clang/libstdc++ (Linux) and Apple clang/libc++ and gcc 7.2
From: degski (degski_at_[hidden])
Date: 2018-01-28 00:40:22

On 27 January 2018 at 18:24, Niall Douglas via Boost <boost_at_[hidden]>
wrote:

> My main development environment is MSVC on Windows as it's the lowest
> common denominator usually.

My IDE is VS2017 as well, but Clang/LLVM is doing the job...

> Outcome may cause GCC to sometimes ICE in its unit tests...

Doesn't matter where or how it ICE-es... it simply shouldn't... Your code
might crash, due to logic errors, UB, double free etc... but the compiler
shouldn't ICE... I'm just stating (in your defense actually) that for now
we don't know who the culprit is, but it starts with gcc.

If you want more useful compiler error messages, I would recommend
wholeheartedly Clang/LLVM <https://llvm.org/builds/>... That installer does
not integrate with VS2017 (it does with VS2015 and lower), but it's trivial
to do it manually, I can send you the props and target files (and where to
put them) if you want...

degski