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] LTO produces randomly ordered debug information
Date: Wed, 11 Feb 2015 11:42:00 -0000 [thread overview]
Message-ID: <bug-65015-4-9k6QwT6ipi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65015-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65015
--- Comment #2 from conchur at web dot de ---
Created attachment 34724
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34724&action=edit
Mini Testcases
Current results (the -COMPILE things are just out of curiosity):
SIMPLE-COMPILE: OK
SIMPLE-LINK: OK
LTO-COMPILE: FAIL
LTO-LINK: FAIL
LTO-OBJDUMP: OK
LTO-EXTERNAL-DEBUG: FAIL
LTO-STRIP-LINK: FAIL
LTO-STRIP-EXTERNAL-DEBUG: FAIL
LTO-BUILDID-LINK: FAIL
LTO-SAVETEMPS-LINK: OK
LTO-SAVETEMPS-EXTERNAL-DEBUG: OK
The -save-temps was a suggestion by Jérémy Bobbio and shows that there is still
a problem with the random file names when trying to use LTO to create
reproducible builds. At least for the simple one file case
>From gcc-bugs-return-476824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 11 11:42:12 2015
Return-Path: <gcc-bugs-return-476824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1281 invoked by alias); 11 Feb 2015 11:42:12 -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 1232 invoked by uid 48); 11 Feb 2015 11:42:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65015] LTO produces randomly ordered debug information
Date: Wed, 11 Feb 2015 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-65015-4-U6oHlHoH7S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65015-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/msg01157.txt.bz2
Content-length: 1400
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide015
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2015-02-11
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
int main()
{
return 0;
}
gcc t.c -g -flto
produces
<0><166>: Abbrev Number: 1 (DW_TAG_compile_unit)
<167> DW_AT_producer : (indirect string, offset: 0x181): GNU GIMPLE
5.0
.0 20150128 (experimental) [trunk revision 220205] -mtune=generic -march=x86-64
-mtune=generic -march=x86-64 -g -fmath-errno -fsigned-zeros -ftrapping-math
-fno
-trapv -fno-strict-overflow -fno-openmp -fno-openacc
-fltrans-output-list=/tmp/c
cmHsiT8.ltrans.out -fltrans
<16b> DW_AT_language : 12 (ANSI C99)
<16c> DW_AT_name : (indirect string, offset: 0x29b):
/tmp/ccmHsiT8.ltrans0.o
which has both tmpfile names in DW_AT_producer and DW_AT_name. I have a fix
for the first issue, but I'm not sure what to use for DW_AT_name. For
-flto-partition=none we get sth like /tmp/ccxWIAkj.o while for regular
LTO we get /tmp/cctZHL25.ltrans0.o. I can use simple plain "WPA" and "LTRANS".
next prev parent reply other threads:[~2015-02-11 11:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 10:11 [Bug lto/65015] New: " conchur at web dot de
2015-02-11 11:42 ` conchur at web dot de [this message]
2015-02-11 12:01 ` [Bug lto/65015] " 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-9k6QwT6ipi@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).