From: "H . J . Lu" <hjl@valinux.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Ulrich Drepper <drepper@cygnus.com>,
John Marvin <jsm@udlkern.fc.hp.com>,
parisc-linux@puffin.external.hp.com,
parisc-linux@thepuffingroup.com, binutils@sourceware.cygnus.com
Subject: Re: [parisc-linux] Use of the EI_OSABI field
Date: Tue, 21 Nov 2000 16:53:27 -0800 [thread overview]
Message-ID: <20001121165327.A12804@valinux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011221042300.16860-100000@front.linuxcare.com.au>; from alan@linuxcare.com.au on Wed, Nov 22, 2000 at 11:13:29AM +1100
On Wed, Nov 22, 2000 at 11:13:29AM +1100, Alan Modra wrote:
>
> > Anyway, the ABI value is zero unless you implement ELF extensions.
>
> Exactly what is an "ELF extension"? Anything outside gABI or
ELF extension is something whose interpretation is not documented in
neither gABI nor psABI. HP's old ELF is a good example since it didn't
implement DT_INIT/DT_FINI, but added DT_INIT_ARRARY/DT_FINI_ARRAY. A
normal ELF tool will have a hard time to interpret those fields and
their values.
H.J.
next prev parent reply other threads:[~2000-11-22 0:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 5:47 [parisc-linux] Use of the EI_OSABI field John Marvin
2000-11-21 22:50 ` Alan Modra
2000-11-21 23:27 ` Ulrich Drepper
2000-11-22 0:13 ` Alan Modra
2000-11-22 0:31 ` Ulrich Drepper
2000-11-22 0:53 ` H . J . Lu [this message]
2000-11-22 3:03 ` Alan Modra
2000-11-22 3:11 ` H . J . Lu
2000-11-25 20:28 ` David O'Brien
2000-11-25 20:33 ` H . J . Lu
2000-11-22 3:18 ` Ulrich Drepper
2000-11-25 20:31 ` David O'Brien
2000-11-25 20:22 ` David O'Brien
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 8:52 John Marvin
2000-11-22 18:06 Cary Coutant
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=20001121165327.A12804@valinux.com \
--to=hjl@valinux.com \
--cc=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=drepper@cygnus.com \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@puffin.external.hp.com \
--cc=parisc-linux@thepuffingroup.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