Re: GCC 5.x, specifically section [2] https://gcc.gnu.org/gcc-5/changes.html#offload
Although these changes are great, I'm not sure we currently need them for Mesos itself. I agree with you that they could make lots of frameworks rock, and I don't think the gcc version for mesos prevents that: - We use protobufs to communicate between services which allows: - Executors can be compiled using a totally different compiler from Apache Mesos - Frameworks can be compiled using a totally different compiler from Apache Mesos - This means you can have a super optimized custom executor that takes advantage of all the benefits of GCC 5.X running on a Mesos built on GCC 4.8 or Clang 3.5! Hopefully this clarifies why this is not actually crucial, and why you won't be missing out on any benefits! Joris On Tue, Apr 21, 2015 at 10:27 AM, Cody Maloney <c...@mesosphere.io> wrote: > The main holdup at the moment is simply cycles I have to convert our > internal infrastructure for packaging mesos on all the distributions to use > newer compilers on all those distributions. I want the infrastructure for > supporting the change in place before we make it. I have about 1/3 of the > work done (Can build on all distros except Debain Wheezy). I've gotta add > the packaging steps (Shouldn't be too bad), and some glue code still > though. > > On Tue, Apr 21, 2015 at 3:07 AM, Alex Rukletsov <a...@mesosphere.com> > wrote: > > > Folks, let's summarize and move on here. > > > > Proposal out on April 9, 2015. Current status (as of April 21, 2015): > > > > > > +1 (Binding) > > ------------------------------ > > Vinod Kone > > Timothy Chen > > Yan Xu > > Brenden Matthews > > > > +1 (Non-binding) > > ------------------------------ > > Cody Maloney > > Joris Van Remoortere > > Jeff Schroeder > > Jörg Schad > > Elizabeth Lingg > > Alexander Rojas > > Alex Rukletsov > > Michael Park > > Haosdent Huang > > Bernd Mathiske > > > > 0 (Non-binding) > > ------------------------------ > > Nikolaos Ballas > > > > There were no -1 votes. > > > > Cody, let's convert MESOS-2604 to an epic and bump the version in 0.23. > > > > Thanks, > > Alex > > > > > > On Mon, Apr 13, 2015 at 12:46 PM, Bernd Mathiske <be...@mesosphere.io> > > wrote: > > > >> +1 > >> > >> > On Apr 10, 2015, at 6:02 PM, Michael Park <mcyp...@gmail.com> wrote: > >> > > >> > +1 > >> > > >> > On 9 April 2015 at 17:33, Alexander Gallego <agall...@concord.io> > >> wrote: > >> > > >> >> This is amazing for native devs/frameworks. > >> >> > >> >> Sent from my iPhone > >> >> > >> >>> On Apr 9, 2015, at 5:16 PM, Joris Van Remoortere < > jo...@mesosphere.io > >> > > >> >> wrote: > >> >>> > >> >>> +1 > >> >>> > >> >>>> On Thu, Apr 9, 2015 at 2:14 PM, Cody Maloney <c...@mesosphere.io> > >> >> wrote: > >> >>>> As discussed in the last community meeting, we'd like to bump the > >> >> minimum required compiler version from GCC 4.4 to GCC 4.8. > >> >>>> > >> >>>> The overall goals are to make Mesos development safer, faster, and > >> >> reduce the maintenance burden. Currently a lot of stout has different > >> >> codepaths for Pre-C++11 and Post-C++11compilers. > >> >>>> > >> >>>> Progress will be tracked in the JIRA: MESOS-2604 > >> >>>> > >> >>>> The resulting supported compiler versions will be: > >> >>>> GCC 4.8, GCC 4.9 > >> >>>> Clang 3.5, Clang 3.6 > >> >>>> > >> >>>> For reference > >> >>>> Compilers by Distribution Version: http://goo.gl/p1t1ls > >> >>>> > >> >>>> C++11 features supported by each compiler: > >> >>>> https://gcc.gnu.org/projects/cxx0x.html > >> >>>> http://clang.llvm.org/cxx_status.html > >> >>> > >> >> > >> > >> > > >
