From: malc <av1474@comtv.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] x86 MMX register access problem seen on Sparc host
Date: Mon, 22 Sep 2008 00:49:06 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0809220048160.2403@linmac.oyster.ru> (raw)
In-Reply-To: <f43fc5580809210120ubc350afq764dd412d2dec7a@mail.gmail.com>
On Sun, 21 Sep 2008, Blue Swirl wrote:
> Hi,
>
> I get these warnings when compiling i386 targets on Sparc host using a
> gcc 4.3 series compiler:
> /src/qemu/target-i386/ops_sse.h: In function 'helper_pmovmskb_mmx':
> /src/qemu/target-i386/ops_sse.h:982: warning: array subscript is above
> array bounds
> etc.
>
> The first line is the following:
> val |= (s->XMM_B(0) >> 7);
All the lines before #if SHIFT == 1 should be MMX_B really.
>
> In cpu.h, the macro is defined on big endian host as
> #define XMM_B(n) _b[15 - (n)]
>
> But the type of Reg argument is MMXReg for pmovmskb_mmx and then the
> _b array has only 8 items.
>
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2008-09-21 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 8:20 [Qemu-devel] x86 MMX register access problem seen on Sparc host Blue Swirl
2008-09-21 20:49 ` malc [this message]
2008-09-21 21:44 ` malc
2008-10-01 12:38 ` Aurelien Jarno
2008-10-01 17:26 ` malc
2008-11-15 11:02 ` Aurelien Jarno
2008-11-15 19:11 ` 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=Pine.LNX.4.64.0809220048160.2403@linmac.oyster.ru \
--to=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).