On Wednesday, March 11, 2015 at 8:40:46 AM UTC, Mike Hommey wrote:
> On Tue, Mar 10, 2015 at 07:23:36PM -0700, Brian Smith wrote:
> > <bo...@mozilla.com> wrote:
> > > In summary: Officially make gcc-4.7 our minimum supported version. Fx38 
> > > and 39 don't compile with 4.6 and none of the GNU/Linux package 
> > > maintainers I have contacted have any major concerns over dropping it.
> > 
> > I propose that either:
> > 
> > (1) GCC 4.8 be made the minimum supported version immediately, or

*snip*

> > > I've contacted the package maintainers for Debian, Red Hat, openSUSE, 
> > > SLES and Ubuntu and they either don't have a problem with dropping 4.6 
> > > or, at least, no more of a problem than the fact we've already dropped 
> > > 4.4.
> > 
> > Did any of them state a preference for not going to GCC 4.8? If so,
> > what was the reasoning?
> 
> At least for Debian, current stable can't build security updates with
> more than 4.7.

In addition, as I understand it:
* openSUSE still has supported versions with gcc-4.7
* SLES (on older versions without 4.6 or 4.7) use a special stack of packages 
to build Firefox which includes gcc-4.7
* Ubuntu 12.04 LTS has 4.6, but are happy to build with a later version as long 
as there are no runtime issues
* Older versions of RHEL are still on gcc-4.4, so they are already going to 
have to do something for Fx37 anyway and moving to 4.7 instead of 4.6 would 
probably not cause too much extra pain.

I don't know how much more work moving to gcc-4.8 would cause, but it would 
certainly be some.

Also, from what I can tell of the C++ features that gcc-4.8 enables (from [1]), 
none of them are available until MSVC 2015.
It seems likely that we'll be supporting MSVC 2013 until the next ESR, so I 
don't see that moving to 4.8 gives us any immediate benefits.

[1] https://developer.mozilla.org/en-US/docs/Using_CXX_in_Mozilla_code
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to