From: Paolo Bonzini <pbonzini@redhat.com>
To: chengang@emindsoft.com.cn
Cc: qemu-devel@nongnu.org, Chen Gang <gang.chen.5i5j@gmail.com>,
ehabkost@redhat.com, rth@twiddle.net
Subject: Re: [PATCH] target: i386: Check float overflow about register stack
Date: Fri, 21 Feb 2020 09:58:27 +0100 [thread overview]
Message-ID: <a5533719-7ef1-938b-e52c-20711e65417f@redhat.com> (raw)
In-Reply-To: <20200221034547.5215-1-chengang@emindsoft.com.cn>
On 21/02/20 04:45, chengang@emindsoft.com.cn wrote:
> static inline void fpush(CPUX86State *env)
> {
> - env->fpstt = (env->fpstt - 1) & 7;
> - env->fptags[env->fpstt] = 0; /* validate stack entry */
> + set_fpstt(env, env->fpstt - 1, false, true);
On overflow fpstt is ~0, so this does:
env->foverflow = true;
env->fpstt = 7;
env->fptags[7] = 0; /* validate stack entry */
Is this correct? You are going to set ST0 so the register should not be
marked empty.
> static inline void fpop(CPUX86State *env)
> {
> - env->fptags[env->fpstt] = 1; /* invalidate stack entry */
> - env->fpstt = (env->fpstt + 1) & 7;
> + set_fpstt(env, env->fpstt + 1, true, true);
While here:
env->foverflow = true;
env->fptags[7] = 1;
env->fpstt = 0;
> void helper_fdecstp(CPUX86State *env)
> {
> - env->fpstt = (env->fpstt - 1) & 7;
> + set_fpstt(env, env->fpstt - 1, false, false);
This is clearing env->foverflow. But after 8 consecutive fdecstp or
fincstp the result of FXAM should not change.
> env->fpus &= ~0x4700;
> }
>
> void helper_fincstp(CPUX86State *env)
> {
> - env->fpstt = (env->fpstt + 1) & 7;
> + set_fpstt(env, env->fpstt + 1, true, false);
Same here.
The actual bug is hinted in helper_fxam_ST0:
/* XXX: test fptags too */
I think the correct fix should be something like
diff --git a/target/i386/fpu_helper.c b/target/i386/fpu_helper.c
index 99f28f267f..792a128a6d 100644
--- a/target/i386/fpu_helper.c
+++ b/target/i386/fpu_helper.c
@@ -991,7 +991,11 @@ void helper_fxam_ST0(CPUX86State *env)
env->fpus |= 0x200; /* C1 <-- 1 */
}
- /* XXX: test fptags too */
+ if (env->fptags[env->fpstt]) {
+ env->fpus |= 0x4100; /* Empty */
+ return;
+ }
+
expdif = EXPD(temp);
if (expdif == MAXEXPD) {
if (MANTD(temp) == 0x8000000000000000ULL) {
Paolo
next prev parent reply other threads:[~2020-02-21 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 3:45 [PATCH] target: i386: Check float overflow about register stack chengang
2020-02-21 8:58 ` Paolo Bonzini [this message]
2020-02-21 14:09 ` Chen Gang
2020-02-21 16:18 ` Paolo Bonzini
2020-02-22 2:10 ` Chen Gang
2020-02-22 2:27 ` Chen Gang
2020-02-22 7:37 ` Paolo Bonzini
2020-02-22 12:25 ` Chen Gang
2020-02-24 12:43 ` Paolo Bonzini
2020-02-25 1:22 ` Chen Gang
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=a5533719-7ef1-938b-e52c-20711e65417f@redhat.com \
--to=pbonzini@redhat.com \
--cc=chengang@emindsoft.com.cn \
--cc=ehabkost@redhat.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).