Bug#796845: marked as done (Uses gcc-4.8 on s390x and m68k)

2015-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2015 11:00:16 + with message-id <e1zwmoy-0003st...@franck.debian.org> and subject line Bug#796845: fixed in linux 4.2-1~exp1 has caused the Debian Bug report #796845, regarding Uses gcc-4.8 on s390x and m68k to be marked as done. This means that you

Bug#796845: Uses gcc-4.8 on s390x and m68k

2015-08-24 Thread Moritz Muehlenhoff
Source: linux Severity: important On s390x and m68k, gcc-4.8 is used which will not be released with stretch (#765380), so the severity of this bug will be bumped when we get closer to the release (m68k isn't RC of course). On a related note, ia64 used gcc-4.6, which was removed from the archive

Re: Bug#765380: don't ship gcc-4.8 with jessie

2014-10-20 Thread Ben Hutchings
enough for jessie. Don't ship legacy compilers with jessie. Hi Matthias, Removing GCC 4.8 will need Linux kernel ABI transitions. I haven't seen any discussion on the debian-kernel list, and the latest of the Linux package (uploaded to sid this week) still has it generating

Re: Bug#765380: don't ship gcc-4.8 with jessie

2014-10-17 Thread Steve Cotton
On Tue, Oct 14, 2014 at 05:25:13PM +0200, Matthias Klose wrote: Package: src:gcc-4.8 Version: 4.8.3-11 Severity: serious Tags: sid jessie The current default for GCC (4.9) is good enough for jessie. Don't ship legacy compilers with jessie. Hi Matthias, Removing GCC 4.8 will need Linux

Re: Bug#765380: don't ship gcc-4.8 with jessie

2014-10-17 Thread Matthias Klose
. Hi Matthias, Removing GCC 4.8 will need Linux kernel ABI transitions. I haven't seen any discussion on the debian-kernel list, and the latest of the Linux package (uploaded to sid this week) still has it generating linux-compiler-* packages depending on gcc-4.8, so I think the Linux

Bug#691576: [reverse-bisected] GDB stops with SIGTRAP at 0 address fixed with GCC 4.8

2014-07-25 Thread Émeric MASCHINO
Hi, Please have a look at upstream bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61799 I was asked to test GCC 4.8 and found this issue go away with locally-recompiled GCC 4.8.2 (upstream source, as ia64 is no more supported by Debian). Whether this was expected or not, I don't know

Re: gcc 4.8

2013-09-05 Thread Bastian Blank
On Mon, Jun 24, 2013 at 07:55:23PM +0100, Ben Hutchings wrote: On Mon, Jun 24, 2013 at 07:27:24PM +0200, Bastian Blank wrote: I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default

Re: gcc 4.8

2013-06-26 Thread Rtp
Ben Hutchings b...@decadent.org.uk writes: Hi, On Mon, Jun 24, 2013 at 07:27:24PM +0200, Bastian Blank wrote: Hi I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default pretty

gcc 4.8

2013-06-24 Thread Bastian Blank
Hi I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default pretty fast for all architectures. Bastian -- Change is the essential process of all existence. -- Spock, Let

Re: gcc 4.8

2013-06-24 Thread Ben Hutchings
On Mon, Jun 24, 2013 at 07:27:24PM +0200, Bastian Blank wrote: Hi I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default pretty fast for all architectures. I think Arnaud said