From: malc <av1474@comtv.ru>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: Torbjorn Granlund <tg@gmplib.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bug report about x86 'bt' insn
Date: Sat, 6 Nov 2010 22:25:16 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1011062223590.2139@linmac> (raw)
In-Reply-To: <alpine.LNX.2.00.1011062220180.1907@linmac>
On Sat, 6 Nov 2010, malc wrote:
> On Sat, 6 Nov 2010, Nathan Froyd wrote:
>
> > On Sat, Nov 06, 2010 at 07:24:39PM +0100, Torbjorn Granlund wrote:
> > > malc <av1474@comtv.ru> writes:
> > >
> > > ZF is undefined according to AMD's 24594.pdf page 69.
> > >
> > > Ah, you're right. It seems that all existing x86 implementations leave
> > > ZF alone, though. (I am not arguing that qeum is broken, the bug is in
> > > my code.)
> >
> > FWIW, the Intel manuals (253666, June 2010) state that the ZF flag is
> > unaffected, not just undefined.
>
> (3-94 Vol. 2A BT it Test)
>
> Flags Affected
> The CF flag contains the value of the selected bit. The OF, SF, ZF, AF,
> and PF flags are undefined.
>
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.
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2010-11-06 19:25 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 [this message]
2010-11-10 14:15 ` Torbjorn Granlund
2010-11-10 14:19 ` malc
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.1011062223590.2139@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).