public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: How to get the padding size for the next section?
Date: Fri, 12 May 2006 17:05:00 -0000	[thread overview]
Message-ID: <20060512053950.GA26440@lucon.org> (raw)

We don't handle .eh_frame section padding properly:

http://sourceware.org/bugzilla/show_bug.cgi?id=2655

When we pad the current .eh_frame section for the alignment of the
next .eh_frame section, we need to know the padding size. Otherwise,
the last FDE size may be wrong. Currently, we assume that all .eh_frame
sections have the same alignment. It isn't true for x86-64 since
the .eh_frame section in crtend.o from gcc has 4 byte alignment.
Ideally, _bfd_elf_write_section_eh_frame knows the real alignment of
the next .eh_frame section. But this info is hard to come by.

A kludge may be to force 8 byte alignment on .eh_frame for x86-64
when we see a 4 byte alignment.


H.J.

                 reply	other threads:[~2006-05-12  5:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060512053950.GA26440@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sources.redhat.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).