public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Andreas Schwab <schwab@suse.de>
Cc: Steve Ellcey <sje@cup.hp.com>, binutils@sources.redhat.com
Subject: Re: copy_private_bfd_data in bfd/elf.c question
Date: Sat, 22 Jun 2002 22:05:00 -0000	[thread overview]
Message-ID: <20020623050552.GN1505@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <jeofe3dso1.fsf@sykes.suse.de>

On Sat, Jun 22, 2002 at 09:23:10PM +0200, Andreas Schwab wrote:
> Alan Modra <amodra@bigpond.net.au> writes:
> 
> |> On Fri, Jun 21, 2002 at 06:28:10PM +0200, Andreas Schwab wrote:
> |> > Steve Ellcey <sje@cup.hp.com> writes:
> |> > 
> |> > |> > How about posting before/after output of readelf -S -l, so we can
> |> > |> > have a clue as to what is going on.
> |> 
> |> Note to Steve: -l not -I !  I was curious as to whether the segment
> |> map changed.  If it didn't then no matter.
> |> 
> |> > |>   [ 4] .hash             HASH            04000620 000620 0000a4 00   A  0   0  8
> |> [snip]
> |> > |>   [ 4] .hash             HASH            04000620 00061c 0000a4 04   A  2   0  8
> |> > 
> |> > This seems to be the culprit.
> |> 
> |> sizeof_hash_entry == 4, so why does this matter?
> 
> But align == 8, and addr and off don't agree in the low 3 bits.

OK, it's different, but why does it matter?  Is there something that
says section alignment should affect file alignment?  I'm more worried
about Steve's report that objcopy resulted in a file that segv'd than
in a file that was different in what seems to me a fairly
insignificant way.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2002-06-23  5:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21  8:26 Steve Ellcey
2002-06-21  9:28 ` Andreas Schwab
2002-06-22  4:56   ` Alan Modra
2002-06-22 12:23     ` Andreas Schwab
2002-06-22 22:05       ` Alan Modra [this message]
2002-06-22 22:11         ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2002-07-23  9:13 Steve Ellcey
2002-07-23  9:43 ` Daniel Jacobowitz
2002-07-23 11:00   ` Nick Clifton
2002-07-16 16:04 Reva Cuthbertson
     [not found] ` <m3vg7cvz6j.fsf@north-pole.nickc.cambridge.redhat.com>
     [not found]   ` <3D3C766C.91969D78@cup.hp.com>
2002-07-23  5:13     ` Nick Clifton
2002-06-28 16:06 Reva Cuthbertson
2002-06-29 10:30 ` Andreas Schwab
2002-07-08 14:16   ` Reva Cuthbertson
2002-06-24  8:49 Steve Ellcey
2002-06-20 10:14 Steve Ellcey
2002-06-20 20:54 ` 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=20020623050552.GN1505@bubble.sa.bigpond.net.au \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=schwab@suse.de \
    --cc=sje@cup.hp.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).