From: Julian Seward <jseward@acm.org>
To: l_indien@magic.fr
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: emu errors for creqv,crnand,crnor,crorc ?
Date: Wed, 31 Oct 2007 14:39:04 +0100 [thread overview]
Message-ID: <200710311439.04939.jseward@acm.org> (raw)
In-Reply-To: <1193837243.24629.22.camel@jma4.dev.netgem.com>
> > way around. Below is a simple test case. On QEMU it prints
> >
> > result is 000fc000
> >
> > and on a real 7447
> >
> > result is 00004000
> >
> What is strange is that 0xFC + 0x04... I will have to check all the CR
> ops, I guess...
Another strange thing is that 000fc000 does not have 'fc' byte-aligned
inside CR, if you see what I mean. If it was 0000fc00 or 00fc0000, some
byte-inversion mistake would seem likely.
This isn't a 74xx specific result. I'm sure any ppc should produce
00004000. The test is very simple: make CR=0 then do crorc 17,14,15.
So only 1 bit in CR will then be set - all others are zero.
J
next prev parent reply other threads:[~2007-10-31 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 11:37 [Qemu-devel] emu errors for creqv,crnand,crnor,crorc ? Julian Seward
2007-10-31 13:27 ` [Qemu-devel] " Jocelyn Mayer
2007-10-31 13:39 ` Julian Seward [this message]
2007-10-31 13:56 ` Jocelyn Mayer
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=200710311439.04939.jseward@acm.org \
--to=jseward@acm.org \
--cc=l_indien@magic.fr \
--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).