Hi,
On my local dev branch, I use C++14, but I don’t have the opportunity to
compile/test all the possible Scons targets.
Before April, we could upload a [WIP] patch on Gerrit with the new compiler
flag(s) and share our thoughts from a different environment and on different
targets.
I agree
Hi all,
In practice, C++14 support should mean g++ version 5 or above or clang 3.4 or
above. Clang supports all C++17 features from version 5, but most features
should be supported from version 3.9 (a large subset is supported in 3.8). GCC
version 7 and above seems to support most of C++17.
Gem5 “historically” sticks to a compiler version that is already part of
shipping LTS distros and RHE or similar[1].
The C++14 right now is implemented in the main LTS distros, and the recent
compiler are full c++14 complaint.
I’d like to reopen the discussion about the general feeling behind
Hi Brandon,
I agree with Andreas. It seems to me that it is a little too soon to
require GCC 6.1. Until we're confident most people's IT infrastructure is
using more recent Linuxes, it's going to be hard to go beyond C++11.
Do you have any suggestions on how to make it simple for all of our
Hi Brandon,
I suggest we stick to a compiler/stdlib version that is already part of
shipping LTS distros and RHE or similar. If I’m not mistaken, for Ubuntu
that means gcc 5.3, and for RHE7 that means gcc 4.8.5.
Andreas
On 14/02/2017, 23:40, "gem5-dev on behalf of Potter, Brandon"
Hello all,
What is the general feeling behind bumping to C++14 instead of keeping the
top-level SConstruct flag at C++11? I would like to use generic lambdas in some
of my code, but cannot do so because it's not available until C++14.
Both GCC and clang support a full implementation of C++14
