public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: binutils@sources.redhat.com
Cc: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Subject: Re: RFA: Don't canonicalize STT_SECTION syms
Date: Sat, 11 Dec 2004 05:38:00 -0000	[thread overview]
Message-ID: <20041211053811.GA3747@nevyn.them.org> (raw)
In-Reply-To: <20041211053202.GM12046@bubble.modra.org>

On Sat, Dec 11, 2004 at 04:02:02PM +1030, Alan Modra wrote:
> On Sat, Dec 11, 2004 at 12:07:29AM -0500, Daniel Jacobowitz wrote:
> > drow@nevyn:~/qtmp% ld -r -o foo foo.o bar.o
> 
> Mutter.  ld -r.  Mutter.

Well, you could get the same result using a final link.

> > 00000000 l    d  foo    00000000 foo
> > 00000000         *UND*  00000000 foo
> > 
> > I'd be really confused!  "Why didn't 'foo' resolve to 'foo'?" the user
> > asks me...
> 
> Well, I'm not wedded to the trick I used.  In fact, I made provision for
> reverting the elfcode.h change without needing to change the testsuite.
> 
> Having the name there does have some benefit, for example with these
> section syms that some targets emit:
> 
> 00000000 l    d  *ABS*	00000000 .shstrtab
> 00000000 l    d  *ABS*	00000000 .symtab
> 00000000 l    d  *ABS*	00000000 .strtab

Hmm, yeah (another note for "weird elf things" volume #37... section
symbols not in a section?  how DOES that work?).

I've been forcibly reminded that STT_SECTION symbols are not, in
principle, all that special.  You could have one with a name, or
without.  Objdump would ideally reveal that difference - though I have
gotten in the habit of using readelf when I need this much precision,
since its output better corresponds to ELF, which is (gasp) better
documented than BFD internals.

How _do_ absolute section symbols work anyway?

-- 
Daniel Jacobowitz

  reply	other threads:[~2004-12-11  5:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 21:50 Daniel Jacobowitz
2004-12-08 23:57 ` Alan Modra
2004-12-10  3:15 ` Hans-Peter Nilsson
2004-12-10  3:21   ` Daniel Jacobowitz
2004-12-10 12:14     ` Alan Modra
2004-12-10 12:56       ` Alan Modra
2004-12-10 14:04         ` Alan Modra
2004-12-10 15:14           ` Hans-Peter Nilsson
2004-12-10 15:19             ` Daniel Jacobowitz
2004-12-11  4:21               ` Alan Modra
2004-12-11  4:34                 ` Daniel Jacobowitz
2004-12-11  4:57                   ` Alan Modra
2004-12-11  5:08                     ` Daniel Jacobowitz
2004-12-11  5:32                       ` Alan Modra
2004-12-11  5:38                         ` Daniel Jacobowitz [this message]
2004-12-11  5:59                           ` Alan Modra
2004-12-11  6:11                             ` Daniel Jacobowitz
2004-12-11  5:52                         ` Alan Modra

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=20041211053811.GA3747@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sources.redhat.com \
    --cc=hans-peter.nilsson@axis.com \
    /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).