From: Richard Henderson <rth@redhat.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Jay.Estabrook@compaq.com, linux-kernel@vger.kernel.org
Subject: Re: [alpha] cleanup opDEC workaround
Date: Tue, 20 Nov 2001 10:47:48 -0800 [thread overview]
Message-ID: <20011120104748.B16422@redhat.com> (raw)
In-Reply-To: <20011119232355.C16091@redhat.com> <20011120133150.A9033@jurassic.park.msu.ru> <20011120090818.A16366@redhat.com> <20011120205105.A15395@jurassic.park.msu.ru>
In-Reply-To: <20011120205105.A15395@jurassic.park.msu.ru>; from ink@jurassic.park.msu.ru on Tue, Nov 20, 2001 at 08:51:05PM +0300
On Tue, Nov 20, 2001 at 08:51:05PM +0300, Ivan Kokshaysky wrote:
> Ok, but with opDEC_fix = 8 we actually skip to addt/stt, so that asm
> probably should be rearranged to ...
No, read the comment and think about it some more.
"fmov $f31, $f0\n\t"
"cvttq/svm $f31, $f31\n\t"
"cmpteq $f31, $f31, $f0\n\t"
"addt $f31, $f31, $f31\n\t"
"stt $f0, %0"
In the broken case, we'll enter entIF with pc==cvttq. Add 8 gives
addt, subtract 4 gives cmpteq, which gives $f0 = 2.0.
In the working case, we'll enter entIF with pc==cmpteq. Add 8 gives
stt, subtract 4 gives addt, which is engineered to be a noop.
> Further, if fp emulation isn't compiled in, we'll have kernel mode
> instruction fault. A quick fix appears to be
Hmm. If fp emulation isn't compiled in, we shouldn't bother
testing this, I think. Means you can't debug fp emulation via
modules on Multia, but I'm pretty sure I don't care.
I suppose the other alternative to get the testing code out of
the normal entIF is to create a custom entIF that is installed
only during opDEC testing. Seems too much work...
r~
next prev parent reply other threads:[~2001-11-20 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 7:23 [alpha] cleanup opDEC workaround 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 [this message]
2001-11-21 12:15 ` Ivan Kokshaysky
2001-11-21 22:27 ` Richard Henderson
2001-11-22 10:55 ` Ivan Kokshaysky
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=20011120104748.B16422@redhat.com \
--to=rth@redhat.com \
--cc=Jay.Estabrook@compaq.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.