From: "VALETTE Eric" <valette@crf.canon.fr>
To: alois_fertl@muenchen.europe.mcd.mot.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC Compiler Problem?
Date: Wed, 1 Dec 1999 17:47:43 +0100 (CET) [thread overview]
Message-ID: <m11tCut-0000WVC@tri-yann.crf.canon.fr> (raw)
In-Reply-To: <384548C4.1E9ADDAF@muenchen.europe.mcd.mot.com> (message from Alois Fertl on Wed, 01 Dec 1999 17:11:48 +0100)
>>>>> "Alois" == Alois Fertl <alois_fertl@muenchen.europe.mcd.mot.com> writes:
Alois> Given the following lines of C, I'd expect that the 4th argument
Alois> is placed into register 6 and 7. As the assembler listing tells,
Alois> register 6 is omitted and the argument goes into r7/r8.
I indeed checked the "PowerPC Processor ABI Supplement" dated September 95
(SVR4 PowerPC ABI) and on 3-18 I see :
For PowerPC, up to eight words are passed in general purpose registers, loaded
sequentially into general purpose registers r3 through r10.
It is clear that this breaks the SVR4 ABI... So you can probably open a bug
report...
The PPC EABI does not differ on that aspect... If someone can point me
to the last spec if I'm wrong...
--
__
/ ` Eric Valette
/-- __ o _. Canon CRF - Communication Dept
(___, / (_(_(__ Rue de la touche lambert
35517 Cesson-Sevigne Cedex
FRANCE
Tel: +33 (0)2 99 87 68 91 Fax: +33 (0)2 99 84 11 30
E-mail: valette@crf.canon.fr http://www.crf.canon.fr
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-01 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-01 16:11 PPC Compiler Problem? Alois Fertl
1999-12-01 16:27 ` Kevin Hendricks
1999-12-01 16:32 ` Gabriel Paubert
1999-12-01 16:47 ` VALETTE Eric [this message]
1999-12-01 17:50 ` Gary Thomas
1999-12-01 17:56 ` VALETTE Eric
1999-12-01 21:59 ` Tony Mantler
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=m11tCut-0000WVC@tri-yann.crf.canon.fr \
--to=valette@crf.canon.fr \
--cc=alois_fertl@muenchen.europe.mcd.mot.com \
--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).