public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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: Fri, 13 Feb 2015 11:24:00 -0000	[thread overview]
Message-ID: <bug-65015-4-nMqa3gopw0@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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Difference in readelf -a is

--- x   2015-02-13 12:04:07.526383914 +0100
+++ y   2015-02-13 12:04:10.158414178 +0100
@@ -234,7 +234,7 @@
     42: 0000000000600df8     0 OBJECT  LOCAL  DEFAULT   19
__do_global_dtors_aux_fin
     43: 0000000000400580     0 FUNC    LOCAL  DEFAULT   13 frame_dummy
     44: 0000000000600df0     0 OBJECT  LOCAL  DEFAULT   18
__frame_dummy_init_array_
-    45: 0000000000000000     0 FILE    LOCAL  DEFAULT  ABS cc5R4C1Y.ltrans0.o
+    45: 0000000000000000     0 FILE    LOCAL  DEFAULT  ABS ccqmAj6c.ltrans0.o
     46: 00000000004005b1    11 FUNC    LOCAL  DEFAULT   13 helper
     47: 0000000000000000     0 FILE    LOCAL  DEFAULT  ABS elf-init.c
     48: 0000000000000000     0 FILE    LOCAL  DEFAULT  ABS crtstuff.c

that is, somehow .symtab contains a reference to the ltrans object file name,
probably because of

        .file   "ccqmAj6c.ltrans0.o"

we emit via output_file_directive. Unfortunately omitting that doesn't help.
It seems that the linker itself adds those symbols!?  HJ?

Gold doesn't do that (thus, it works with -fuse-ld=gold).


  parent reply	other threads:[~2015-02-13 11:24 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 [this message]
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-nMqa3gopw0@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).