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: Fri, 13 Feb 2015 12:45:00 -0000 [thread overview] Message-ID: <bug-65015-4-p3a7yKRyR8@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 conchur at web dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #34746|0 |1 is obsolete| | --- Comment #12 from conchur at web dot de --- Created attachment 34747 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34747&action=edit Mini Testcases > Gold doesn't do that (thus, it works with -fuse-ld=gold). Weird, my gnu gold 2.25-4 (debian version) still shows the symptoms: SIMPLE-LINK: OK SIMPLE-OBJDUMP: OK SIMPLE-EXTERNAL-DEBUG: OK BFD-LTO-LINK: FAIL BFD-LTO-OBJDUMP: FAIL BFD-LTO-EXTERNAL-DEBUG: FAIL NOPART-BFD-LTO-LINK: OK NOPART-BFD-LTO-OBJDUMP: OK NOPART-BFD-LTO-EXTERNAL-DEBUG: OK GOLD-LTO-LINK: FAIL GOLD-LTO-OBJDUMP: FAIL GOLD-LTO-EXTERNAL-DEBUG: FAIL NOPART-GOLD-LTO-LINK: OK NOPART-GOLD-LTO-OBJDUMP: OK NOPART-GOLD-LTO-EXTERNAL-DEBUG: OK Maybe you have a newer gold version installed which already includes a patch which resolves this problem? Diff of bfd: 221c221 < 41: 0000000000000000 0 FILE LOCAL DEFAULT ABS ccsmMmrk.ltrans0.o --- > 41: 0000000000000000 0 FILE LOCAL DEFAULT ABS cctSjrTo.ltrans0.o Diff of gold: 201c201 < 14: 0000000000000000 0 FILE LOCAL DEFAULT ABS cc4lSDuA.ltrans0.o --- > 14: 0000000000000000 0 FILE LOCAL DEFAULT ABS ccxXItKB.ltrans0.o 245c245 < Build ID: a9117c8c1852ec657a0cdd6e206427571bae9b31 --- > Build ID: d65e429c3314089118f114fee1625276ef91835c
next prev parent reply other threads:[~2015-02-13 12:45 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 ` [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 [this message] 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-p3a7yKRyR8@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: linkBe 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).