Path: chuka.playstation.co.uk!news
From: Philip Gooch <philg@easynet.co.uk>
Newsgroups: scee.yaroze.programming.libraries
Subject: Re: SsVabTransfer locks up!
Date: Mon, 20 Jul 1998 13:00:17 +0100
Organization: PlayStation Net Yaroze (SCEE)
Lines: 33
Message-ID: <35B33151.6DE1D612@easynet.co.uk>
References: <359E82E9.1134@dial.pipex.com> <01bdafbf$5c177f20$f2e832a2@gbain.wav.scee.sony.co.uk> <35AF051F.708C@dial.pipex.com> <35AF1307.C1D4198B@scee.sony.co.uk>
NNTP-Posting-Host: 193.131.140.246
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.05 [en] (Win95; I)



James Russell wrote:

> Chris Chadwick wrote:
> >
> > With me, SsVabTransfer() fails but if I comment out the __asm__
> > lines it works fine!
> >
> > Any ideas?
>
> Colin thinks that SsVabTransfer is overflowing the stack on the D-Cache. He also points out that the
> entire program doesn't have to run with the stack on the D-Cache, just the bits you want to run
> really fast.
>

  Anyone mind if I jump in here? Just taking up on your comment here, about putting the stack on the
D-cache - in what cases would you want to do this, and when? Would you put in this code:

        __asm__ volatile ("sw $29,(savesp)");
        __asm__ volatile ("la $29,0x1f8003f0");

   before a particular function call, and this:

        __asm__ volatile ("lw $29,(savesp)");

afterwards? For what sort of functions would I want to do this? Should it be used only sparingly? Can
you give some real-world examples?

Cheers

Phil