Bug#777753: [Reproducible-builds] Bug#777753: gcc: LTO produces unreproducible debug information

2015-02-24 Thread conchur
tags 53 + fixed-upstream thanks Backport for 4.9.x: https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=220935 Backport for 4.8.x: https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=220938 Versions including the fix: 4.8.5, 4.9.3, 5.0 -- To UNSUBSCRIBE, email to

Bug#777753: [Reproducible-builds] Bug#777753: gcc: LTO produces unreproducible debug information

2015-02-18 Thread conchur
I have to correct my last statement. It is still necessary to add -flto-partition=none when using -flto in a package. My earlier statement came from the wrong understanding of buildid as explained in the gcc bug [3]. A new patch [4] was submitted by Richard Biener. Together these patches

Bug#777753: Aw: [Reproducible-builds] Bug#777753: gcc: LTO produces unreproducible debug information

2015-02-13 Thread conchur
The patches are now upstream [1, 2]. The last test [2] showed that these really seemed to be the culprit of the problem. In the meantime, Richard Biener proposed patches which can solve this problem. I've compiled my own version of gcc-4.9 using the attached patch and can confirm that the LTO

Bug#777753: gcc: LTO produces unreproducible debug information

2015-02-12 Thread conchur
affects 53 + apt-cacher-ng affects 53 + avian affects 53 + batctl affects 53 + batmand affects 53 + cloop affects 53 + encfs affects 53 + exactimage affects 53 + kwalletcli affects 53 + makefs affects 53 + mupen64plus-audio-sdl affects 53 + 

Bug#777753: gcc: LTO produces unreproducible debug information

2015-02-12 Thread conchur
Source: gcc-4.9 Version: 4.9.2-10 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness toolchain X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015 The GCC produced binaries seem to