Re: GCC and binutils updates for buster

On Mon, Jul 16, 2018 at 05:59:28PM +0200, Matthias Klose wrote: >... > - armel: The armv4t default isn't used very much anymore, The baseline is armv5te since last year. > and we had issues in the past. Could you elaborate on that? The latest major issue I am aware of was about #727621 and the

Re: GCC and binutils updates for buster

Hi, On 17/07/2018 17:56, Aurelien Jarno wrote: Hi, On 2018-07-16 17:59, Matthias Klose wrote: The Debian release team lists toolchain support for our release architectures, and according to [4], the amd64, i386, armel, armhf, arm64 architectures are supported as primary architectures, and s390

Re: GCC and binutils updates for buster

Hi, On 2018-07-16 17:59, Matthias Klose wrote: > The Debian release team lists toolchain support for our release architectures, > and according to [4], the amd64, i386, armel, armhf, arm64 architectures are > supported as primary architectures, and s390x is supported as a secondary > architectures

GCC and binutils updates for buster

GCC 8 is available in testing/unstable, and upstream is approaching the first point release. I am planning to make GCC 8 the default at the end of the week (gdc and gccgo already point to GCC 8). Most runtime libraries built from GCC are already used in the version built from GCC 8, so I don't ex