|
From: Julian S. <js...@ac...> - 2003-04-02 19:48:19
|
> Now, I notice that in fact my 0x6E is wrong, because the else { } bit
> generates MMX2_RegRd when it should generate MMX2_MemRd.
Duh ... engage brain ...
In fact it's OK, if somewhat longwinded. It gets the address into an
integer register, does a 4-byte load into an int reg, and then moves
that into MMX land with MMX2_RegRd.
So I guess a complete 0x7E implementation can be made by inverting
data flow direction for 0x6E.
J
|
|
From: Jeremy F. <je...@go...> - 2003-04-03 00:50:29
|
On Wed, 2003-04-02 at 11:56, Julian Seward wrote:
> > Now, I notice that in fact my 0x6E is wrong, because the else { } bit
> > generates MMX2_RegRd when it should generate MMX2_MemRd.
>
> Duh ... engage brain ...
>
> In fact it's OK, if somewhat longwinded. It gets the address into an
> integer register, does a 4-byte load into an int reg, and then moves
> that into MMX land with MMX2_RegRd.
>
> So I guess a complete 0x7E implementation can be made by inverting
> data flow direction for 0x6E.
OK, have a look at 88-mmxfix now.
J
|