From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: james@massive.com.au
Cc: randolph@tausq.org, dave@hiauly1.hia.nrc.ca,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] parsic function calling convention
Date: Fri, 17 May 2002 11:58:08 -0400 [thread overview]
Message-ID: <20020517115808.A11603@systemhalted> (raw)
In-Reply-To: <200205171442.g4HEgNbk029843@hiauly1.hia.nrc.ca>; from dave@hiauly1.hia.nrc.ca on Fri, May 17, 2002 at 10:42:22AM -0400
> You will probably need to understand stub generation to implement libffi
> if I recall correctly.
>
> Hpux uses a segmented memory model. Linux uses a flat model.
>
> Dave
Last I remember there was someone porting avcall.
They might be a good resource.
http://lists.debian.org/debian-hppa/2002/debian-hppa-200203/msg00073.html
Here is some general discussion on fp passing:
http://lists.parisc-linux.org/hypermail/parisc-linux/8277.html
c.
prev parent reply other threads:[~2002-05-17 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 1:52 [parisc-linux] parsic function calling convention James Mc Parlane
2002-05-17 4:07 ` Grant Grundler
2002-05-17 6:36 ` Randolph Chung
2002-05-17 14:42 ` John David Anglin
2002-05-17 15:58 ` Carlos O'Donell Jr. [this message]
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=20020517115808.A11603@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=james@massive.com.au \
--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