Bug#845690: gcc-6: gcc creates unbootable kernel on x86-64

Control: reassign -1 binutils 2.27.51.20161124-1 Control: retitle -1 binutils: creates unbootable kernel on x86-64 Control: severity -1 grave On 2016-11-26 15:13 +0100, Damien Wyart wrote: > After running further tests today, I think this is in fact *not* > related to gcc but to the kernel

Bug#845690: binutils 2.27.51.20161124

on ubuntu same problem, after update binutils to 2.27.51.20161124-1ubuntu1 and gcc-6 to 6.2.1-5ubuntu1 gcc-6 6.2.1-4ubuntu1 and binutils 2.27.51.20161118-2ubuntu1 no problem.

Re: Hurd port for gcc go PATCH 1-4(23)

Hello, Nice work! Mmm, why making changes in each file in a separate patch? I don't think it makes things easier to review, I'd say rather send a big patch, it's altogether that it makes sense anyway. > Index: gcc-6-6.2.1-4.1/src/libgo/Makefile.in >

Bug#845690: Same problem here!

On Sat, 26 Nov 2016 21:50:37 +0100 Eric Valette wrote: Screwed up my NAS updating the kernel. Kernel panic just after init. gcc : 6.2.1-1 kernel = upstream 4.4.35 reverting to my own compiled 4.4.33 fixed the problem. Ooops gcc= 6.2.1-5 and kernel is x86-64 -- eric

Bug#845690: Same problem here!

Screwed up my NAS updating the kernel. Kernel panic just after init. gcc : 6.2.1-1 kernel = upstream 4.4.35 reverting to my own compiled 4.4.33 fixed the problem. --eric

gcc-defaults_1.168_amd64.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Nov 2016 17:14:56 +0100 Source: gcc-defaults Binary: cpp gcc gcc-multilib g++ g++-multilib gobjc gobjc-multilib gobjc++ gobjc++-multilib gfortran gfortran-multilib gccgo gccgo-multilib libgcj-common libgcj-bc

Processing of gcc-defaults_1.168_amd64.changes

gcc-defaults_1.168_amd64.changes uploaded successfully to localhost along with the files: gcc-defaults_1.168.dsc gcc-defaults_1.168.tar.gz cpp-aarch64-linux-gnu_7-20161116-1_amd64.deb cpp-arm-linux-gnueabi_7-20161116-1_amd64.deb cpp-arm-linux-gnueabihf_7-20161116-1_amd64.deb

gcc-7_7-20161125-1_amd64.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 25 Nov 2016 12:41:07 +0100 Source: gcc-7 Binary: gcc-7-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-7-dev libgcc4 libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-7-dev lib32gcc1 lib32gcc1-dbg lib32gcc-7-dev

Processed: Re: Processed: Re: Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

Processing control commands: > severity -1 important Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349 Severity set to 'important' from 'serious' > reassign -1 gcc-6 Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in

Bug#845751: Processed: Re: Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

Control: severity -1 important Control: reassign -1 gcc-6 Mathieu, these issues are not RC issues, gcc doesn't become unusable. On 26.11.2016 15:39, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > >> reassign 845751 gcc 4:6.2.1-1 > Bug #845751 [src:yadifa]

Processed: Fwd:

Processing commands for cont...@bugs.debian.org: > reassign 845751 gcc-6 6.2.1-4 Bug #845751 [gcc] yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349 Bug reassigned from package 'gcc' to 'gcc-6'. No longer marked as found in versions gcc-defaults/1.164. Ignoring

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 845751 src:yadifa Bug #845751 [gcc] yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349 Added indication that 845751 affects src:yadifa > End of message, stopping processing here. Please contact me if you

Processed: Re: Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

Processing commands for cont...@bugs.debian.org: > reassign 845751 gcc 4:6.2.1-1 Bug #845751 [src:yadifa] yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349 Bug reassigned from package 'src:yadifa' to 'gcc'. No longer marked as found in versions yadifa/2.2.2-1.

Bug#845690: gcc-6: gcc creates unbootable kernel on x86-64

After running further tests today, I think this is in fact *not* related to gcc but to the kernel itself. I tested all 6.2.1-X versions as well as gcc-5 (5.4.1-3) and all the kernels fail to boot (balck screen just after grub and nothing in the logs). A few days ago (beginning of this week, I

Bug#845751: yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349

Source: yadifa Version: 2.2.2-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=yadifa=ppc64el=2.2.2-1=1480164499 ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./include/dnscore -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -DDNSCORE_BUILD -D_THREAD_SAFE -D_REENTRANT

Bug#845749: libwebp FTBFS on armhf: inlining failed in call to always_inline 'vtrnq_s32': target specific option mismatch

Source: libwebp Version: 0.5.1-3 Severity: serious https://buildd.debian.org/status/logs.php?pkg=libwebp=armhf ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src/webp -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wall -Wdeclaration-after-statement -Wextra

Bug#845377: gdc-6: libdl trouble again

On 26.11.2016 11:38, Peter De Wachter wrote: > Hello Matthias and Iain, > > Is it an expected effect that some programs now need to be build with > -fPIC? For example: > > $ cat >test.d > import std.conv; > void main() { > string b; > float c; > to!int(b); > to!string(c); > } > > $ gdc

Bug#845377: gdc-6: libdl trouble again

Hello Matthias and Iain, Is it an expected effect that some programs now need to be build with -fPIC? For example: $ cat >test.d import std.conv; void main() { string b; float c; to!int(b); to!string(c); } $ gdc -o test test.d /usr/bin/ld: /tmp/cc6LR10G.o: relocation R_X86_64_PC32

Bug#845690: gcc-6: gcc creates unbootable kernel on x86-64

Replying to myself: sorry for the false lead, this is not the same problem. The one from gcc bugtracker is not related to the stable gcc-6 branch used in Debian unstable, so the problem must be somewhere else. The -fno-printf-return-value is not recognized with gcc 6 from Sid. Best regards