Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@parisc-linux.org, will@misconception.org.uk
Subject: Re: [parisc-linux] Re: Fwd: Re: Any hppa gurus?
Date: Tue, 2 Apr 2002 08:47:31 -0500	[thread overview]
Message-ID: <20020402084731.C26273@systemhalted> (raw)
In-Reply-To: <200203302132.g2ULWNcp028559@hiauly1.hia.nrc.ca>; from dave@hiauly1.hia.nrc.ca on Sat, Mar 30, 2002 at 04:32:23PM -0500

> 
> I some situations, the callee needs to save the argument registers on
> the stack.  There are 4 words reserved for this.
> 

Okay. I'll see if I can find those in the documentation.

> > 	int	gr26	fr7	-----		===	float
> > 	int	gr25	fr6	float		===	-----
> > 	---	gr24	fr5	-----		---	-----
> > 	---	gr23	fr4	-----		---	-----
> 
> You've got the order of the float registers reversed.  They are allocated
> in order of increasing number starting with fr4.
> 

Ah! Excellent. After looking at some more assembly output and reading...
I should have realized that it was the other way around :) Thanks.

Now some of my register allocation guessing is coming out correct :}

Serves me right for using complex examples all the time.

c.

      parent reply	other threads:[~2002-04-02 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E16qeEE-0000jh-00.2002-03-28-18-02-27@mail6.svr.pol.co.uk>
     [not found] ` <20020328143202.I12094@systemhalted>
     [not found]   ` <E16qkq2-0008AG-00.2002-03-29-01-05-55@mail7.svr.pol.co.uk>
2002-03-30 15:47     ` [parisc-linux] Re: Fwd: Re: Any hppa gurus? Carlos O'Donell Jr.
2002-03-30 17:36       ` John David Anglin
2002-03-30 20:11         ` Carlos O'Donell Jr.
2002-03-30 21:32           ` John David Anglin
2002-03-30 21:56             ` John David Anglin
2002-04-02 13:47             ` Carlos O'Donell Jr. [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=20020402084731.C26273@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@parisc-linux.org \
    --cc=will@misconception.org.uk \
    /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