Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Cary Coutant <cary@cup.hp.com>
To: <amodra@one.net.au>, "Matthew Wilcox" <willy@ldl.fc.hp.com>
Cc: <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] ELFOSABI_LINUX
Date: Thu, 3 May 2001 10:28:58 -0700	[thread overview]
Message-ID: <200105031731.KAA21930@adlmail.cup.hp.com> (raw)

>  1) We use relocations that are not mentioned in the Processor
>     Specific ABI supplement, eg. R_PARISC_PCREL12F.

What is the relocation number? I'll add it. (I hope it's not 13 or 73. 
We've recently added PCREL17FI and PCREL22FI, respectively.)


>  2) PA-ELF32 uses relocations that the parisc psabi says are only
>     used by ELF64, eg. R_PARISC_IPLT.  No big deal, except of course
>     they're a different size.

Is it still 129? I'll add it.

If there are any other relocations you use that aren't in HP's ELF/PA 
document, please let me know.


>  3) PA-ELF32 uses DT_INIT and DT_FINI, which the psabi specifically
>     says are not used (by HPUX).  Again no big deal.

I agree -- no big deal. The document that says they're not used is 
specifically referring to HP-UX, and was not meant to apply to other 
operating systems.


>  4) HPUX sets a precedent for PARISC, and uses a non-zero OSABI value

Well, we *do* use vendor-specific extensions. Plenty of them, in fact.


-cary

             reply	other threads:[~2001-05-03 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-03 17:28 Cary Coutant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-04 17:05 [parisc-linux] ELFOSABI_LINUX Cary Coutant
2001-05-02 18:10 Cary Coutant
2001-05-04  3:11 ` Ulrich Drepper
2001-05-02  3:34 Matthew Wilcox
2001-05-02 23:47 ` amodra
2001-05-12 16:01 ` Jes Sorensen

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=200105031731.KAA21930@adlmail.cup.hp.com \
    --to=cary@cup.hp.com \
    --cc=amodra@one.net.au \
    --cc=parisc-linux@parisc-linux.org \
    --cc=willy@ldl.fc.hp.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