Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-17 Thread Leif Hedstrom
> On May 9, 2018, at 1:13 AM, Igor Galić wrote: > > > > I would like to propose that we move to C++17 for ATS 8.0.0. This would > require us to move to gcc 7, clang 5, and icc 18 as minimum versions for > C++17 support. > > What does this move our minimum EL distro

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-17 Thread Chris Lemmons
With all the benefits that come with 17, I think there's not a whole lot of point looking backward on this one. There's enough OS support that we can make it happen. +1 On Wed, May 9, 2018 at 1:13 AM, Igor Galić wrote: > > >> > >> I would like to propose that we move to C++17 for ATS 8.0.0. Thi

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-09 Thread Igor Galić
> > >> I would like to propose that we move to C++17 for ATS 8.0.0. This would > > >> require us to move to gcc 7, clang 5, and icc 18 as minimum versions for > > >> C++17 support. > > >> > > >> > > > What does this move our minimum EL distro to? Can we still use 6? > > > > > > > > Also, since w

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-08 Thread Phil Sorber
On Tue, May 8, 2018 at 9:16 AM Alan Carroll wrote: > We're already building on some platforms with C++17, so I don't think we'll > need to do any code updates. The goal is to make future coding easier by > > 1) Removing string_view and ink_std_compat.h > 2) Enable use of C++17 headers like string

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-08 Thread Alan Carroll
We're already building on some platforms with C++17, so I don't think we'll need to do any code updates. The goal is to make future coding easier by 1) Removing string_view and ink_std_compat.h 2) Enable use of C++17 headers like string_view and file_system. 3) Have a single consistent C++ standar

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-08 Thread Phil Sorber
On Tue, May 8, 2018 at 8:43 AM Leif Hedstrom wrote: > > > > On May 7, 2018, at 4:10 PM, Phil Sorber wrote: > > > > On Mon, May 7, 2018 at 9:07 AM Bryan Call wrote: > > > >> I would like to propose that we move to C++17 for ATS 8.0.0. This would > >> require us to move to gcc 7, clang 5, and ic

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-08 Thread Leif Hedstrom
> On May 7, 2018, at 4:10 PM, Phil Sorber wrote: > > On Mon, May 7, 2018 at 9:07 AM Bryan Call wrote: > >> I would like to propose that we move to C++17 for ATS 8.0.0. This would >> require us to move to gcc 7, clang 5, and icc 18 as minimum versions for >> C++17 support. >> >> > What does

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-08 Thread Bryan Call
Devtoolset 7 for RHEL6 has gcc 7. -Bryan > On May 7, 2018, at 4:10 PM, Phil Sorber wrote: > > On Mon, May 7, 2018 at 9:07 AM Bryan Call > wrote: > I would like to propose that we move to C++17 for ATS 8.0.0. This would > require us to move to gcc 7, clang 5, and icc

Re: [PROPOSAL] C++17, gcc 7, and clang 5 for ATS 8.0.0

2018-05-07 Thread Phil Sorber
On Mon, May 7, 2018 at 9:07 AM Bryan Call wrote: > I would like to propose that we move to C++17 for ATS 8.0.0. This would > require us to move to gcc 7, clang 5, and icc 18 as minimum versions for > C++17 support. > > What does this move our minimum EL distro to? Can we still use 6? > -Bryan