From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] run time code generation for IA-64
Date: Tue, 27 May 2003 18:56:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723706048@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723706033@msgid-missing>
>>>>> On Wed, 28 May 2003 00:17:42 +0530 (IST), CH Gowri Kumar <gkumar@csa.iisc.ernet.in> said:
CH> Hi David,
>> Where do you have R4 and R5 before using them?
CH> Did you mean to say that I have to save R4 and R5 before using them?
Yes, of course: "preserved" means you have to save a register before
using it. On the positive side, it's contents will get preserved
across calls.
CH> Just wondering why isn't there a standard calling convention on IA-64.
CH> Something of this sort(if at all to be saved):
CH> rp has to be saved in loc0
CH> sp has to be saved in loc1
CH> gp has to be saved in loc2
That would needlessly constrain code optimization. For example, on
ia64, it's almost never necessary to save sp.
--david
next prev parent reply other threads:[~2003-05-27 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 10:49 [Linux-ia64] run time code generation for IA-64 CH Gowri Kumar
2003-05-27 18:17 ` David Mosberger
2003-05-27 18:42 ` David Mosberger
2003-05-27 18:56 ` David Mosberger [this message]
2003-05-27 18:59 ` CH Gowri Kumar
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=marc-linux-ia64-105590723706048@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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