public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Richard Henderson <rth@redhat.com>
Cc: binutils@sources.redhat.com, Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: ELF DT_HASH hash-table entry size.
Date: Mon, 21 Feb 2005 23:06:00 -0000	[thread overview]
Message-ID: <20050221201631.GA5641@nevyn.them.org> (raw)
In-Reply-To: <20050221192312.GA31162@redhat.com>

On Mon, Feb 21, 2005 at 11:23:12AM -0800, Richard Henderson wrote:
> On Mon, Feb 21, 2005 at 01:27:08PM +1030, Alan Modra wrote:
> > elf64-alpha.c and elf64-s390.c both define a hash entry size of 8.  This
> > violates the ELF spec, which say the entry size is always 4.  Was the
> > alpha and s390 choice deliberate, or is this just an accident?
> 
> Accidental.  BFD was wrong for *all* 64-bit ELF ports at one time.
> Alpha was the only one that had been in general use when the problem
> was discovered and fixed.  But it was too late to change for Alpha
> without breaking binary compatibility.
> 
> Dunno what s390's excuse is.
> 
> > Note that using a size of 8 has practical difficulties:  An executable
> > without a section header has no way to communicate to generic ELF tools
> > like readelf (via sh_ent_size) that the hash table is unusual.
> 
> Huh?  An executable without a section header?  If you don't have a 
> section header then you don't have a symbol table, so the point is
> moot.

Doesn't it also apply to .dynsym?

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-02-21 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 11:51 Alan Modra
2005-02-21 21:51 ` Richard Henderson
2005-02-21 23:06   ` Daniel Jacobowitz [this message]
2005-02-21 23:54     ` Richard Henderson
2005-02-22  1:04   ` 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=20050221201631.GA5641@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sources.redhat.com \
    --cc=rth@redhat.com \
    --cc=schwidefsky@de.ibm.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).