public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Roland McGrath <roland@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	Jakub Jelinek <jakub@redhat.com>,
	Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix tst-array* on x86_64
Date: Tue, 10 Dec 2002 16:56:00 -0000	[thread overview]
Message-ID: <20021210165623.A5106@lucon.org> (raw)
In-Reply-To: <200212110035.gBB0Zs029801@magilla.sf.frob.com>; from roland@redhat.com on Tue, Dec 10, 2002 at 04:35:54PM -0800

On Tue, Dec 10, 2002 at 04:35:54PM -0800, Roland McGrath wrote:
> I already read the linker script of course.  I don't see how that explains
> it.  The ALIGN is done before the symbol or the section.  Ah, but you are
> saying that the section will have sh_addralign of 16 and that will skip the
> word after the symbol and before the section.  Of course, you didn't say
> that so I can only assume that having me just get lucky and guess what you
> meant was your way of being helpful.

The linker script shows that __preinit_array_start is aligned by
ALIGN(${ALIGNMENT}). It doesn't matter what alignment .preinit_array
uses. A target has to make sure all __*_array_start are aligned
properly. The current elf.sc assumes ALIGN(${ALIGNMENT}) will align
all __*_array_start correctly. It seems to work for ia32 and ia64.


H.J.

      reply	other threads:[~2002-12-11  0:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  5:52 Jakub Jelinek
2002-12-10  9:43 ` H. J. Lu
2002-12-10 10:06   ` Jakub Jelinek
2002-12-10 10:47 ` Ulrich Drepper
2002-12-10 15:25   ` Roland McGrath
2002-12-10 15:44     ` H. J. Lu
2002-12-10 16:35       ` Roland McGrath
2002-12-10 16:56         ` H. J. Lu [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=20021210165623.A5106@lucon.org \
    --to=hjl@lucon.org \
    --cc=drepper@redhat.com \
    --cc=jakub@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@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).