From: Ian Lance Taylor <ian@wasabisystems.com>
To: Jason Spencer <spencer8@sbcglobal.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: debugging gcc-generated assembly
Date: Wed, 08 Sep 2004 20:23:00 -0000 [thread overview]
Message-ID: <m3acw04ijb.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040908201413.19789.qmail@web81608.mail.yahoo.com>
Jason Spencer <spencer8@sbcglobal.net> writes:
> I'm trying to chase a nasty bug in code generated by
> GCC 2.7.2 on a Motorola PowerPC 603 core. I have to
> understand the register usage conventions the compiler
> uses, but I can't find that in any of the docs.
> Specifically, I'm interested in things like which
> register is the "this" pointer, which are used for
> parameters, return values, etc. Is there an easily
> accessible doc that goes through those details for my
> architecture?
See the "Function Calling Sequence" chapter in
http://www.linuxbase.org/spec/ELF/ppc64/PPC-elf64abi-1.7.html
The "this" pointer is normally treated as an invisible first
argument.
Ian
prev parent reply other threads:[~2004-09-08 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 20:14 Jason Spencer
2004-09-08 20:23 ` Ian Lance Taylor [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=m3acw04ijb.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=gcc-help@gcc.gnu.org \
--cc=spencer8@sbcglobal.net \
/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).