public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "conchur at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65015] New: LTO produces randomly ordered debug information
Date: Wed, 11 Feb 2015 10:11:00 -0000	[thread overview]
Message-ID: <bug-65015-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015

            Bug ID: 65015
           Summary: LTO produces randomly ordered debug information
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: conchur at web dot de

I was discussing with the Debian Reproducible Builds people some problem that
I've noticed (only) with LTO builds. The build id (and debug link) was changing
all the time and Jérémy Bobbio suggested that one reason for this problem are
the odd filenames in the debug sections.

I was able to workaround this special problem by using -flto-partition=none

But now I still have differences in the debug sections. I tried to narrow it
down, uncompressed it and found out that both files have the same size. And
things like the debug_str sections have common parts but oddly (random?)
ordered.

This currently makes LTO unsuitable for reproducible builds on Debian (amd64,
and most likely all other architectures).

I was not able to find any related bug in the meta bug #47819. Maybe it should
be added there. My discussion of the findings can be found at
http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150209/000933.html
>From gcc-bugs-return-476806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 11 10:11:18 2015
Return-Path: <gcc-bugs-return-476806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26996 invoked by alias); 11 Feb 2015 10:11:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26921 invoked by uid 48); 11 Feb 2015 10:11:15 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64824] ICE in gimple verification
Date: Wed, 11 Feb 2015 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64824-4-0igag4ejJ1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg01139.txt.bz2
Content-length: 360

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd824

--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Jakub Jelinek from comment #5)
> What does #c3 have to do with this?

Same ice, so I guessed same problem.

>I don't see any OpenMP pragmas in your code, therefore it can't be related to >this.  File a new PR?

Done. #65014


             reply	other threads:[~2015-02-11 10:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 10:11 conchur at web dot de [this message]
2015-02-11 11:42 ` [Bug lto/65015] " conchur at web dot de
2015-02-11 12:01 ` rguenth at gcc dot gnu.org
2015-02-11 12:24 ` rguenth at gcc dot gnu.org
2015-02-12  8:42 ` conchur at web dot de
2015-02-12  8:56 ` rguenth at gcc dot gnu.org
2015-02-13  9:36 ` rguenth at gcc dot gnu.org
2015-02-13  9:36 ` rguenth at gcc dot gnu.org
2015-02-13 10:18 ` conchur at web dot de
2015-02-13 11:24 ` rguenth at gcc dot gnu.org
2015-02-13 11:25 ` rguenth at gcc dot gnu.org
2015-02-13 12:45 ` conchur at web dot de
2015-02-13 13:42 ` hjl.tools at gmail dot com
2015-02-13 16:16 ` rguenther at suse dot de
2015-02-13 17:30 ` hjl.tools at gmail dot com
2015-02-13 19:32 ` hjl.tools at gmail dot com
2015-02-13 20:06 ` hjl.tools at gmail dot com
2015-02-14  0:36 ` hjl.tools at gmail dot com
2015-02-16 10:06 ` rguenth at gcc dot gnu.org
2015-02-16 10:08 ` rguenth at gcc dot gnu.org
2015-02-16 14:53 ` rguenth at gcc dot gnu.org
2015-02-16 14:53 ` rguenth at gcc dot gnu.org
2015-02-18  9:26 ` conchur at web dot de
2015-02-24  9:24 ` rguenth at gcc dot gnu.org
2015-02-24  9:27 ` rguenth at gcc dot gnu.org
2015-02-24 12:15 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-65015-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).