I'm using

options casemap:none

I see lots of code here like:

pxor mm0,mm0

I will get an error unless I use:

pxor MM0,MM0

I'm using the latest MASM package.

If you think this is a dumb, question...
:eek: :eek: I've been working for 18 hours:eek: :eek:

Good time for dumb questions.:grin:
Posted on 2002-04-08 16:01:11 by ThoughtCriminal
Yes, I agree those small caps are confusing. But they actually use a text equate for that.


mm0 TEXTEQU <MM0>
mm1 TEXTEQU <MM1>
mm2 TEXTEQU <MM2>
mm3 TEXTEQU <MM3>
mm4 TEXTEQU <MM4>
mm5 TEXTEQU <MM5>
mm6 TEXTEQU <MM6>
mm7 TEXTEQU <MM7>
There's also one trick for mm0 to work perfectly without text equates. That is to remove OPTION CASEMAP:NONE and remove also the include for windows.inc because if you don't you'll get an error on windows.inc.

Same thing goes for the FPU most of the codes you'll see in the algo section are st(0), st(1)... In fact there is no such thing as st(1)...There are only St, St(1)...The first letter should be capitalize and the second one should be in lowercase. I think there is a macro for this one too but I can't find it.
Posted on 2002-04-08 16:38:29 by stryker
I included in Windows.inc
mm0 equ MM(0)
etc.
also wrote there another "shorts" like
offs equ offset
dpt equ dword ptr
bpt equ byte ptr
... etc.
Posted on 2002-04-08 17:01:17 by The Svin
Actually, if you put

.XMM

...at the top of your file, you can use lowercase.
Posted on 2002-04-08 20:06:13 by bitRAKE
Just tried the .XMM, no go. I think I'll use The Svin's method and just add to window inc. Nice and transparent.

Thanks for the info.
Posted on 2002-04-09 02:55:03 by ThoughtCriminal
Strange? Maybe it's .686, or version 7.0 of ML.EXE? I'll play with it some more and let you know what the determining factor is. (I was sure it was the .XMM?)
Posted on 2002-04-09 09:49:04 by bitRAKE