From: Alan Modra <amodra@bigpond.net.au>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Nick Clifton <nickc@redhat.com>,
wilson@specifixinc.com, Jan Beulich <JBeulich@novell.com>,
binutils@sources.redhat.com
Subject: Re: [PATCH] ELF: make .struct interact with .previous
Date: Sun, 17 Apr 2005 23:34:00 -0000 [thread overview]
Message-ID: <20050417233405.GA13413@bubble.modra.org> (raw)
In-Reply-To: <20050416004357.GB16052@lucon.org>
On Fri, Apr 15, 2005 at 05:43:57PM -0700, H. J. Lu wrote:
> On Fri, Apr 15, 2005 at 05:36:47PM -0700, H. J. Lu wrote:
> > On Sat, Apr 16, 2005 at 07:30:16AM +0930, Alan Modra wrote:
> > > On Fri, Apr 15, 2005 at 11:37:18AM -0700, H. J. Lu wrote:
> > > > I don't think we should call md_cons_align for ABS section. This patch
> > > > fixes the failure.
> > >
> > > Why not? If you need to do something special for the absolute section,
> > > then md_cons_align itself should handle that.
> >
> > What special alignment can a backend can do for the absolute section?
> >
>
> There are
>
> @item md_cons_align
> @cindex md_cons_align
> You may define this macro to do any special alignment before a data
> allocation pseudo-op.
>
> But there is no data allocation involved for the absolute section.
The struct test is using a .short, which looks like a data allocation
pseudo-op to me. If .short should have different alignment when you
happen to use it in the absolute section, then md_cons_align should
reflect that fact.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-04-17 23:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 13:41 Jan Beulich
2005-04-15 10:52 ` Nick Clifton
2005-04-15 17:31 ` H. J. Lu
2005-04-15 18:37 ` H. J. Lu
2005-04-15 22:00 ` Alan Modra
2005-04-16 0:36 ` H. J. Lu
2005-04-16 0:44 ` H. J. Lu
2005-04-17 23:34 ` Alan Modra [this message]
2005-04-18 1:15 ` H. J. Lu
2005-04-18 7:57 Jan Beulich
2005-04-18 13:47 ` H. J. Lu
2005-04-18 20:12 ` James E Wilson
2005-04-19 21:27 ` H. J. Lu
2005-04-18 14:13 Jan Beulich
2005-04-20 7:12 Jan Beulich
2005-04-20 9:31 ` Nick Clifton
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=20050417233405.GA13413@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=JBeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=nickc@redhat.com \
--cc=wilson@specifixinc.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).