From: Cary Coutant <cary@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IA64 ELF header question...
Date: Tue, 22 Jan 2002 22:26:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805916@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805902@msgid-missing>
>Since PPC64 and IA64 share the use of function
>descriptors, I thought I'd check with people here on how this
>was solved for IA64. Anyone have any ideas I can use?
PA-RISC also uses function descriptors. On HP-UX, for both PA-RISC and
IA-64, the e_entry field is the address of the code entry point itself,
rather than the address of a function descriptor. Our dynamic loader
initializes its own gp value, and when it's time for the dynamic loader
to call the application's entry point, it knows what the gp value should
be, so we don't need a function descriptor.
Cary Coutant
HP-UX Runtime Architect
next prev parent reply other threads:[~2002-01-22 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 18:48 [Linux-ia64] IA64 ELF header question Peter Bergner
2002-01-22 22:26 ` Cary Coutant [this message]
2002-01-24 13:51 ` Peter Bergner
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=marc-linux-ia64-105590698805916@msgid-missing \
--to=cary@cup.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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