From: malc <av1474@comtv.ru>
To: Torbjorn Granlund <tg@gmplib.org>
Cc: qemu-devel@nongnu.org, Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [Qemu-devel] Bug report about x86 'bt' insn
Date: Wed, 10 Nov 2010 17:19:30 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1011101717260.1854@linmac> (raw)
In-Reply-To: <86bp5xb6y8.fsf@shell.gmplib.org>
On Wed, 10 Nov 2010, Torbjorn Granlund wrote:
> malc <av1474@comtv.ru> writes:
>
> And this one was March 2009 (conveniently having the same file name
> 253666), the September 2010 issue reads differently:
>
> Flags Affected
> The CF flag contains the value of the selected bit. The ZF flag is
> unaffected. The OF, SF, AF, and PF flags are undefined.
>
> Have the qemu developers come to any decision on this one?
>
> I haven't tested many 32-bit x86 implementations, but I think I have
> tested all 64-bit x86 implementations, and they all seem to leave ZF
> unaffected. (Clearly, it is possible that they do write it for some
> values of the operands; there are too many possible values to test.)
>
> I actually think qemu for both x86-32 and x86-64 should be changed to
> make the bt insn not affect ZF. Considering that Intel have changed
> their manuals (I have confirmed this) to say that ZF is unaffected,
> there are even stronger reasons to change qemu. Even without that
> documentation change, I would argue that compatibility with all defacto
> hardware is important.
>
All is the keyword here, i doubt that exhaustive search was performed
furthermore, AMDs documentation (to the best of my knowledge still)
still maintains that ZF is undefined.
That said the bt operation should be changed but for different reasons.
> (I am not trying to say that my bug report was correct. It wasn't. I
> have fixed the GMP code.)
>
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2010-11-10 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 14:42 [Qemu-devel] Bug report about x86 'bt' insn Torbjorn Granlund
2010-11-06 17:16 ` malc
2010-11-06 18:24 ` Torbjorn Granlund
2010-11-06 18:55 ` malc
2010-11-06 18:59 ` Nathan Froyd
2010-11-06 19:22 ` malc
2010-11-06 19:25 ` malc
2010-11-10 14:15 ` Torbjorn Granlund
2010-11-10 14:19 ` malc [this message]
2010-11-10 14:38 ` Torbjorn Granlund
2010-11-10 15:08 ` malc
2010-11-10 15:45 ` malc
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=alpine.LNX.2.00.1011101717260.1854@linmac \
--to=av1474@comtv.ru \
--cc=froydnj@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=tg@gmplib.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 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).