From: Avi Kivity <avi@redhat.com>
To: malc <av1474@comtv.ru>
Cc: Daniil Troshkov <904308@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 904308] [NEW] x86: BT/BTS/BTR/BTC: ZF flag is unaffected
Date: Wed, 14 Dec 2011 18:28:08 +0200 [thread overview]
Message-ID: <4EE8CE98.1050200@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1112142021390.2362@linmac>
On 12/14/2011 06:22 PM, malc wrote:
> On Wed, 14 Dec 2011, Avi Kivity wrote:
>
> > On 12/14/2011 06:08 PM, malc wrote:
> > > On Wed, 14 Dec 2011, Daniil Troshkov wrote:
> > >
> > > > Public bug reported:
> > > >
> > > > Hello!
> > > >
> > > > Bug was found in qemu.git.
> > > > See target-i386/translate.c:
> > > >
> > >
> > > [..snip..]
> > >
> > > Intel's documentation doesn't cover this, AMD's says that ZF is undefined, so,
> > > question is: why do you think QEMU is wrong here?
> >
> > The Intel documentation states that ZF is unaffected.
> >
>
> Right, i was blind, anyways, AMD disagrees.
>
Best to be conservative here.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-14 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:47 [Qemu-devel] [Bug 904308] [NEW] x86: BT/BTS/BTR/BTC: ZF flag is unaffected Daniil Troshkov
2011-12-14 15:47 ` [Qemu-devel] [Bug 904308] " Daniil Troshkov
2011-12-14 15:58 ` Peter Maydell
2011-12-14 16:08 ` [Qemu-devel] [Bug 904308] [NEW] " malc
2011-12-14 16:18 ` Avi Kivity
2011-12-14 16:22 ` malc
2011-12-14 16:28 ` Avi Kivity [this message]
2011-12-14 16:33 ` malc
2011-12-14 17:42 ` Avi Kivity
2011-12-14 16:45 ` [Qemu-devel] [Bug 904308] " Daniil Troshkov
2017-06-10 6:33 ` Thomas Huth
2017-08-10 4:17 ` Launchpad Bug Tracker
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=4EE8CE98.1050200@redhat.com \
--to=avi@redhat.com \
--cc=904308@bugs.launchpad.net \
--cc=av1474@comtv.ru \
--cc=qemu-devel@nongnu.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).