Re: [Valgrind-users] FD leakage

[Nicholas N. <nj...@ca...>]

On Mon, 5 Jan 2004, John Reiser wrote:

> >>                                                     and the continuing
> >>unimplemented SSE/SSE2/3DNow! opcodes (including prefixes 0x66, 0xF2, 0xF3).
> >
> >
> > There is pretty good coverage of these now I think. We certainly don't
> > seem to be seeing many reports of this now and the ones we do get are
> > usually patched fairly quickly and short of a volunteer to go through
> > the architecture reference manual and implement any missing instructions
> > it isn't clear what more could be done.
>
> The first thing that could be done is count the number of architected
> opcodes (including prefixes) that remain unimplemented.  Put that number
> in the user-level documentation, put the specific list and classification
> of the missing cases and a suggested order of implementation in the developer
> documentation, and _then_ ask for volunteers.  Advertising the specifics
> is much more likely to create interest than a vague "there are some
> unimplemented opcodes."

See attachment for a list of unimplemented MMX/SSE/SSE2 opcodes.  About
78% are implemented.  The list may contain mistakes;  the names and
opcodes of these instructions can be confusing, and I wasn't as thorough
as I could have been.  Still, it should give a good idea of what's left.
As for a suggested order of implementation, I won't pretend to know,
however the fact that users haven't reported them yet indicate the ones
remaining aren't used very widely.

N