[Top] [All Lists]

Re: implementation of software suspend on MIPS. (system log)

To: Hyon Lim <>
Subject: Re: implementation of software suspend on MIPS. (system log)
From: "J. Scott Kasten" <>
Date: Wed, 31 Oct 2007 22:27:31 -0400
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=Received:X-YMail-OSG:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To:Message-ID:References:MIME-Version:Content-Type; b=VeJJhY2mLtbp9GND6o0+eblWWNAD72OGWlAqdRja6wQwfuxmyGt72OgTSlT3mSoPc76uAM1cp2sBl+OKp0PQGMf0Z73whct4+VsTSlVuMEw3a1/Tjsd8O2/KWxNnREq3eWsrc/ktAvdd9Ga+7K/Sd/aNWI1Fu+tukjDpvvjtpeg= ;
In-reply-to: <>
Original-recipient: rfc822;
References: <> <>

On Thu, 1 Nov 2007, Hyon Lim wrote:

Yes. you're right. I did same as you said.
However, is there any options for disassembly with variable name?
Often I cannot find that variable's allocated register.
There is only r0,r1... but I want a comment for variable assignment status.

I just have to ask the question, but is it really necessary to code the whole thing in assembly? I understand that the interface probably does need to be, but the main body of the function? If it's very large or complicated, it would seem simpler to use C and write assembly glue to pull it all together rather than trying to debug hand assembly. Many of us here have spent hours before tracking down problems with stale data in branch delay slots. The compiler is a tad more convienient.



<Prev in Thread] Current Thread [Next in Thread>