From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Richard Henderson <rth@redhat.com>
Cc: Jay.Estabrook@compaq.com, linux-kernel@vger.kernel.org
Subject: Re: [alpha] cleanup opDEC workaround
Date: Thu, 22 Nov 2001 13:55:50 +0300 [thread overview]
Message-ID: <20011122135550.A15090@jurassic.park.msu.ru> (raw)
In-Reply-To: <20011119232355.C16091@redhat.com> <20011120133150.A9033@jurassic.park.msu.ru> <20011120090818.A16366@redhat.com> <20011120205105.A15395@jurassic.park.msu.ru> <20011120104748.B16422@redhat.com> <20011121151555.A20128@jurassic.park.msu.ru> <20011121142753.A876@redhat.com>
In-Reply-To: <20011121142753.A876@redhat.com>; from rth@redhat.com on Wed, Nov 21, 2001 at 02:27:53PM -0800
On Wed, Nov 21, 2001 at 02:27:53PM -0800, Richard Henderson wrote:
> Actually, the custom entIF isn't that much work. What about this?
Hmm, I like it.
However, if I didn't missed something again, some corrections are required.
First, in opDEC_check_entIF r16 should be stored on the stack frame
(PAL_rti will restore it). Also, if SRM is broken and doesn't update pc,
we'll jump back to cvttq/svm. So I think we need something like this:
opDEC_check_entIF: \n\
ldq $16,8($sp) \n\
+ stq $16,24($sp) \n\
+ addq $16,4,$16 \n\
+ stq $16,8($sp) \n\
call_pal 63 /* PAL_rti */ \n\
and
"cvttq/svm $f31, $f31\n\t"
+ "nop\n\t"
"subq $16, %0, %0"
No?
Ivan.
prev parent reply other threads:[~2001-11-22 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 7:23 Richard Henderson
2001-11-20 10:31 ` Ivan Kokshaysky
2001-11-20 17:08 ` Richard Henderson
2001-11-20 17:51 ` Ivan Kokshaysky
2001-11-20 18:47 ` Richard Henderson
2001-11-21 12:15 ` Ivan Kokshaysky
2001-11-21 22:27 ` Richard Henderson
2001-11-22 10:55 ` Ivan Kokshaysky [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=20011122135550.A15090@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=Jay.Estabrook@compaq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@redhat.com \
/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
all inboxes | Powered by JetHome®