Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Jeff Bailey <jbailey@raspberryginger.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] ELF ABI Documents
Date: Tue, 18 Apr 2006 11:00:24 +0800	[thread overview]
Message-ID: <44445648.5050004@tausq.org> (raw)
In-Reply-To: <1145324814.24150.12.camel@localhost.localdomain>

> It's most common in the LSB specs to refer to the ELF psabi document
> where possible.  http://refspecs.freestandards.org/elf/elf-pa.pdf seems
> to be a copy of the psabi document, but when checking with some folks,
> it looks like the document isn't a reflection on reality for
> parisc-linux.  The question is, should the document be updated to
> reflect reality, should we slowly change to match the document, or
> should I just not refer to the psabi document much when writing the LSB
> document?

First of all, I want to say that such a document would be wonderful to have!

I think the ELF-PA document corresponds mostly with what we do on
parisc-linux. There are some things we don't implement (e.g. I don't
think we have PCREL14WR/PCREL14DR), and we have made some enhancements
in other areas (e.g. TLS relocations). The only thing that I know of
where we don't follow the spec is how we handle SEGREL32 - we don't use
a SEGBASE relocation to set the segment base, but rely on other
information from the ELF headers.

I don't think the ELF spec talks about calling conventions and syscall
conventions though. For that, parisc-linux mostly follows the SOM spec
for calling conventions
(http://ftp.parisc-linux.org/docs/arch/pa-runtime-32-SOM.pdf)

A document about hppa ABI will not be complete without some discussion
about the hppa unwinding mechanism too.

my 2 cents :)
randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2006-04-18  3:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18  1:46 [parisc-linux] ELF ABI Documents Jeff Bailey
2006-04-18  3:00 ` Randolph Chung [this message]
2006-04-18  3:11   ` Jeff Bailey
2006-04-18 14:36     ` John David Anglin
2006-04-18 18:46       ` Carlos O'Donell
2006-04-20  8:56       ` Matt Taggart
2006-04-20 14:23         ` John David Anglin
2006-04-20  0:45 ` John David Anglin

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=44445648.5050004@tausq.org \
    --to=randolph@tausq.org \
    --cc=jbailey@raspberryginger.com \
    --cc=parisc-linux@lists.parisc-linux.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