From: Alan Modra <amodra@bigpond.net.au>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com, richard@codesourcery.com
Subject: Re: PATCH: PR ld/2655/2657: Incorrrect padding for .eh_frame section
Date: Wed, 24 May 2006 12:16:00 -0000 [thread overview]
Message-ID: <20060524021830.GB18928@bubble.grove.modra.org> (raw)
In-Reply-To: <20060513174131.GB7805@lucon.org>
On Sat, May 13, 2006 at 10:41:31AM -0700, H. J. Lu wrote:
> We shouldn't pad the .eh_frame section to its section alignment.
Where it was being done is too late anyway. Patch OK.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
prev parent reply other threads:[~2006-05-24 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 1:07 Incorrect assumption on the CIE/FDE alignment H. J. Lu
2006-05-13 17:42 ` PATCH: PR ld/2655/2657: Incorrrect padding for .eh_frame section H. J. Lu
2006-05-15 2:03 ` H. J. Lu
2006-05-15 3:19 ` H. J. Lu
2006-05-24 12:16 ` Alan Modra [this message]
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=20060524021830.GB18928@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=richard@codesourcery.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).