Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: linker debug info editing
Date: Sun, 12 Mar 2006 07:58:00 -0000	[thread overview]
Message-ID: <8f2776cb0603101744w3dd59741s4ad8e17b7069a6fa@mail.gmail.com> (raw)
In-Reply-To: <20060310124921.GN6777@bubble.grove.modra.org>

After you've chosen dies to delete, how do you deal with other dies
that refer to the deleted dies?  I'm not talking about parents; I'm
talking about attributes whose form is DW_FORM_ref*.

I think the information we need to do this reduction correctly isn't
available at the level you're working at.  linkonce sections aren't
really deleted; they're unified.  The data in them doesn't go away;
equivalent data from elsewhere is used instead.

I tend to think that having the compiler divide the information into
separate compilation units, as Jim suggests, is the only way to go
here.  In that scenario, inter-CU references will use symbols to refer
to their targets; after choosing which instance of the linkonce
section to keep, you should still have definitions for all the symbols
the other dies' relocs refer to.

As Daniel says, the GDB-related reasons for avoiding this solution are
long gone.


  parent reply	other threads:[~2006-03-11  1:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 19:44 Alan Modra
2006-03-10 20:06 ` James E Wilson
2006-03-10 20:16   ` Daniel Jacobowitz
2006-03-12  7:58 ` Jim Blandy [this message]
2006-03-13 12:53   ` Daniel Berlin
2006-03-13 20:19     ` Alan Modra
2006-03-14 15:10     ` Daniel Berlin
2006-03-13  4:59 ` Daniel Jacobowitz

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=8f2776cb0603101744w3dd59741s4ad8e17b7069a6fa@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.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