From: dickg@develcon.com (Dick Ginther)
To: help-gcc@gnu.org
Subject: PowerPC Stack Frames
Date: Mon, 06 Dec 1999 09:05:00 -0000 [thread overview]
Message-ID: <82gpv3$bjn@sirius.develcon.com> (raw)
Hi,
I am using egcs-2.91.66 for a PowerPC. I would like
some help understanding how registers and the stack are used
on PowerPC with GCC. I know that R1 is the stack pointer, but
are there other registers reserved for other purposes?
On an interrupt do I have to save all 32 registers or
are there a sub-set that are usually used.
Thanks in advance.
--
Dick Ginther E-mail: dick.ginther@develcon.com
Develcon Electronics Ltd. Web: http://www.develcon.com
856 - 51st Street East Phone: 306 931-1339
Saskatoon, SK Canada S7K 5C7 Fax: 306 931-1352
WARNING: multiple messages have this Message-ID
From: dickg@develcon.com (Dick Ginther)
To: help-gcc@gnu.org
Subject: PowerPC Stack Frames
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <82gpv3$bjn@sirius.develcon.com> (raw)
Message-ID: <19991231222400.CEe6mQHhqKtydOgB5G0BeVmoTgPo1Z2P5o4xYOMDWMs@z> (raw)
Hi,
I am using egcs-2.91.66 for a PowerPC. I would like
some help understanding how registers and the stack are used
on PowerPC with GCC. I know that R1 is the stack pointer, but
are there other registers reserved for other purposes?
On an interrupt do I have to save all 32 registers or
are there a sub-set that are usually used.
Thanks in advance.
--
Dick Ginther E-mail: dick.ginther@develcon.com
Develcon Electronics Ltd. Web: http://www.develcon.com
856 - 51st Street East Phone: 306 931-1339
Saskatoon, SK Canada S7K 5C7 Fax: 306 931-1352
next reply other threads:[~1999-12-06 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-06 9:05 Dick Ginther [this message]
1999-12-06 13:06 ` Andrew Klossner
1999-12-31 22:24 ` Andrew Klossner
1999-12-09 11:44 ` Frank Herold
1999-12-31 22:24 ` Frank Herold
1999-12-31 22:24 ` Dick Ginther
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='82gpv3$bjn@sirius.develcon.com' \
--to=dickg@develcon.com \
--cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).