From: Aurelien Jarno <aurelien@aurel32.net>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] x86 MMX register access problem seen on Sparc host
Date: Sat, 15 Nov 2008 12:02:25 +0100 [thread overview]
Message-ID: <20081115110225.GA8325@hall.aurel32.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0810012124540.9679@linmac.oyster.ru>
On Wed, Oct 01, 2008 at 09:26:18PM +0400, malc wrote:
> On Wed, 1 Oct 2008, Aurelien Jarno wrote:
>
> >On Mon, Sep 22, 2008 at 01:44:55AM +0400, malc wrote:
> >>On Mon, 22 Sep 2008, malc wrote:
> >>
> >>>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.
> >>
> >>Scratch that. It should be this instead:
> >
> >Acked-By: <aurelien@aurel32.net>
> >
> >Care to commit the patch?
>
> Fabrice was CCed, but i haven't heard his opinion.
>
Any news on that? I think the patch could be committed in any case.
Otherwise we will forget it. I can commit it if you prefer.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
next prev parent reply other threads:[~2008-11-15 11:02 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
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 [this message]
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=20081115110225.GA8325@hall.aurel32.net \
--to=aurelien@aurel32.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).