From: Jeff Bailey <jbailey@raspberryginger.com>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] ELF ABI Documents
Date: Mon, 17 Apr 2006 23:11:23 -0400 [thread overview]
Message-ID: <1145329883.24150.17.camel@localhost.localdomain> (raw)
In-Reply-To: <44445648.5050004@tausq.org>
[-- Attachment #1.1: Type: text/plain, Size: 783 bytes --]
Le mardi 18 avril 2006 à 11:00 +0800, Randolph Chung a écrit :
> 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)
Right. This is where the LSB document comes it. It does wind up
defining those for Linux at least. The "Mostly follows SOM" is largely
what's inspired me on this quest. I'd love to see a definitive document
that defines this and am willing to go through the effort to do it.
Tks,
Jeff Bailey
--
Although when you're in the situation that RMS is telling you that
you're being too ideological about freedom, maybe, just maybe, it's
true.
- Matthew Wilcox
[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-04-18 3:11 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
2006-04-18 3:11 ` Jeff Bailey [this message]
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=1145329883.24150.17.camel@localhost.localdomain \
--to=jbailey@raspberryginger.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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