Switch default GCC to 4.8 on s390x

[Aurelien Jarno]

Hi all,

The s390x architecture is still using GCC 4.6 as the default compiler,
while most other architectures have already switched to GCC 4.8. It
starts to cause problem for building packages: some packages need
C11 features to be compiled, while some others assume the default
compiler is already GCC 4.8 (in that case they are actually buggy). It
would also help having the same default version of GCC than for GCJ, GDC
or GFORTRAN.

I therefore propose to switch the default compiler on s390x to GCC 4.8
by default. It is already used to build the kernel without any known
issue.

Any comments or opinion on that?

Best regards,
Aurelien

[Matthias Klose]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Aurelien Jarno
Hi all,
The s390x architecture is still using GCC 4.6 as the default compiler,
while most other architectures have already switched to GCC 4.8. It starts
to cause problem for building packages: some packages need C11 features to
be compiled, while some others assume the default compiler is already GCC
4.8 (in that case they are actually buggy). It would also help having the
same default version of GCC than for GCJ, GDC or GFORTRAN.
I therefore propose to switch the default compiler on s390x to GCC 4.8 by
default. It is already used to build the kernel without any known issue.
Any comments or opinion on that?

Is this a commitment from Philipp, Bastian or your side to monitor for s390x
specific toolchain issues, forward these upstream and feed these back into Debian?

Matthias

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKJyy4ACgkQStlRaw+TLJwQGQCfd6wETFZutdAdfPZQEnX2KhVa
z9kAmwdkwmbge78wuh+a9Jqb+81Q8AaT
=vzb7
-----END PGP SIGNATURE-----

[Aurelien Jarno]

Post by Matthias Klose

Post by Aurelien Jarno
Hi all,
The s390x architecture is still using GCC 4.6 as the default compiler,
while most other architectures have already switched to GCC 4.8. It starts
to cause problem for building packages: some packages need C11 features to
be compiled, while some others assume the default compiler is already GCC
4.8 (in that case they are actually buggy). It would also help having the
same default version of GCC than for GCJ, GDC or GFORTRAN.
I therefore propose to switch the default compiler on s390x to GCC 4.8 by
default. It is already used to build the kernel without any known issue.
Any comments or opinion on that?

Is this a commitment from Philipp, Bastian or your side to monitor for s390x
specific toolchain issues, forward these upstream and feed these back into Debian?

It is a commitment from my side, although s390x is well tested upstream
and there is therefore not a lot to do.

Note that I have just done the change in the SVN, it would be nice if
you can upload gcc-defaults.

Best regards,
Aurelien

[Matthias Klose]

Post by Matthias Klose

Post by Aurelien Jarno
Hi all,
The s390x architecture is still using GCC 4.6 as the default compiler,
while most other architectures have already switched to GCC 4.8. It
starts to cause problem for building packages: some packages need C11
features to be compiled, while some others assume the default compiler
is already GCC 4.8 (in that case they are actually buggy). It would
also help having the same default version of GCC than for GCJ, GDC or
GFORTRAN.
I therefore propose to switch the default compiler on s390x to GCC 4.8
by default. It is already used to build the kernel without any known
issue.
Any comments or opinion on that?

Is this a commitment from Philipp, Bastian or your side to monitor for
s390x specific toolchain issues, forward these upstream and feed these
back into Debian?

It is a commitment from my side, although s390x is well tested upstream and
there is therefore not a lot to do.

please update debian/README.Debian in gcc-4.8.

[Aurelien Jarno]

Post by Matthias Klose

Post by Matthias Klose

Post by Aurelien Jarno
Hi all,
The s390x architecture is still using GCC 4.6 as the default compiler,
while most other architectures have already switched to GCC 4.8. It
starts to cause problem for building packages: some packages need C11
features to be compiled, while some others assume the default compiler
is already GCC 4.8 (in that case they are actually buggy). It would
also help having the same default version of GCC than for GCJ, GDC or
GFORTRAN.
I therefore propose to switch the default compiler on s390x to GCC 4.8
by default. It is already used to build the kernel without any known
issue.
Any comments or opinion on that?

Is this a commitment from Philipp, Bastian or your side to monitor for
s390x specific toolchain issues, forward these upstream and feed these
back into Debian?

It is a commitment from my side, although s390x is well tested upstream and
there is therefore not a lot to do.

please update debian/README.Debian in gcc-4.8.

Done. That said I still don't understand why only a limited list of
architectures have to do that. I do not believe that architectures not
listed there are actually better supported in Debian.

[Matthias Klose]

Post by Aurelien Jarno

Post by Matthias Klose

Post by Aurelien Jarno

Post by Matthias Klose

Post by Aurelien Jarno
Hi all,
The s390x architecture is still using GCC 4.6 as the default
compiler, while most other architectures have already switched to
GCC 4.8. It starts to cause problem for building packages: some
packages need C11 features to be compiled, while some others assume
the default compiler is already GCC 4.8 (in that case they are
actually buggy). It would also help having the same default version
of GCC than for GCJ, GDC or GFORTRAN.
I therefore propose to switch the default compiler on s390x to GCC
4.8 by default. It is already used to build the kernel without any
known issue.
Any comments or opinion on that?

Is this a commitment from Philipp, Bastian or your side to monitor
for s390x specific toolchain issues, forward these upstream and feed
these back into Debian?

It is a commitment from my side, although s390x is well tested upstream
and there is therefore not a lot to do.

please update debian/README.Debian in gcc-4.8.

Done. That said I still don't understand why only a limited list of
architectures have to do that. I do not believe that architectures not
listed there are actually better supported in Debian.

It's the other way around. Every architecture should have an entry. But maybe
it is easier to mention which architectures currently don't have such entries,
namely sparc, s390, ia64, powerpc, ppc64.

x86 should be waived. we do have active contributors for kfreebsd, the hurd,
m68k, alpha, powerpcspe, mips64, hppa at least. arm* is missing here, but it
is usually taken care of by myself.

Matthias

[Aurelien Jarno]

Post by Matthias Klose

Post by Aurelien Jarno

Post by Matthias Klose

Post by Aurelien Jarno

Post by Matthias Klose

Post by Aurelien Jarno
Hi all,
The s390x architecture is still using GCC 4.6 as the default
compiler, while most other architectures have already switched to
GCC 4.8. It starts to cause problem for building packages: some
packages need C11 features to be compiled, while some others assume
the default compiler is already GCC 4.8 (in that case they are
actually buggy). It would also help having the same default version
of GCC than for GCJ, GDC or GFORTRAN.
I therefore propose to switch the default compiler on s390x to GCC
4.8 by default. It is already used to build the kernel without any
known issue.
Any comments or opinion on that?

Is this a commitment from Philipp, Bastian or your side to monitor
for s390x specific toolchain issues, forward these upstream and feed
these back into Debian?

It is a commitment from my side, although s390x is well tested upstream
and there is therefore not a lot to do.

please update debian/README.Debian in gcc-4.8.

Done. That said I still don't understand why only a limited list of
architectures have to do that. I do not believe that architectures not
listed there are actually better supported in Debian.

It's the other way around. Every architecture should have an entry. But maybe
it is easier to mention which architectures currently don't have such entries,
namely sparc, s390, ia64, powerpc, ppc64.

s390 is dead and is still only available for squeeze and wheezy, so it
doesn't matter for jessie and sid.

Post by Matthias Klose
x86 should be waived. we do have active contributors for kfreebsd, the hurd,
m68k, alpha, powerpcspe, mips64, hppa at least.

If they have active contributors, I think they should also be noted
there, otherwise this file is more than useless. Or we should remove
mips and s390x entries.

Post by Matthias Klose
arm* is missing here, but it
is usually taken care of by myself.

Well then why you don't add yourself there? Note that they are a few
worrying bugs on armel like #628063, #697521, #727621 that have not been
forwarded upstream yet.