From: David Edelsohn <dje@watson.ibm.com>
To: Charles Lepple <clepple@mitre.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PowerPC assembly question
Date: Thu, 08 Jul 1999 14:32:55 -0400 [thread overview]
Message-ID: <9907081832.AA28950@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Charles Lepple <clepple@mitre.org> of "Thu, 08 Jul 1999 13:39:17 EDT." <3784E245.8930A1B4@mitre.org>
>>>>> Charles Lepple writes:
Charles> I've been poking around with some disassembled C code, and I'm wondering
Charles> if there is a source of documentation on register usage guidelines
Charles> (maybe an ABI? I'm just not used to this concept of passing arguments in
Charles> registers as opposed to the stack). Any help would be appreciated.
All of this is defined in the appropriate ABI (AIX PowerOpen and
SVR4 PowerPC ABI). The ABI specifies the uses of each register when
targeting code to the calling convention (argument passing, volatile and
non-volatile registers, etc.)
David
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-08 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.990708091154.18399B-100000@liberty.chnd1.az.home.com>
1999-07-08 16:25 ` PREP IDE support is broken Matt Porter
1999-07-08 17:39 ` PowerPC assembly question Charles Lepple
1999-07-08 17:54 ` Josh Huber
1999-07-08 18:32 ` David Edelsohn [this message]
1999-07-09 7:40 ` PREP IDE support is broken VALETTE Eric
1999-07-08 18:37 PowerPC assembly question Charles A. Jolley
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=9907081832.AA28950@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=clepple@mitre.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).