[Nasm-devel] documentation

[Frank K. <fbk...@ne...>]

Don't all speak at once!

Nelson Rush said:
> You`ve updated the nasm documents to reflect the changes I presume?

Documents? Updated? What good news *that* would be!

I've "updated" the official Nasm Docs for 0.98 (same as docs for 0.97,
pretty much, I think) to at least list the "KATMAI" and "3DNow!"
instructions supported by 0.98 but not mentioned in the docs. There are
other features that appear in the source but not in the docs - debugger
support for Borland (?) and the "-m" switch, e.g. My progress so far is
at:
http://www.geocities.com/SiliconValley/Heights/1295/

The current html output works on my drive, but not on-line - gotta look
into that.

So, are the following instructions supported in the "new" version? (I
forget who sent me the link, but thanks!)

------------------------------------------------------------
http://homepage1.nifty.com/herumi/soft/gogo2/readme_e.txt

 (9) APPENDIX ( How to make NASM supporting Enhanced 3D Now! )

  Append the following source to insns.dat and make, and you get NASM
which
  can assemble Enhanced 3D Now!.
  At own your RISK, get
http://homepage1.nifty.com/herumi/soft/nasm098-e3dn.lzh
  for Windows. (NO WARRANTY!)

--- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8
--- x8 --- x8 ---
PI2FD     mmxreg,mem          \301\2\x0F\x0F\110\01\x0D    
PENT,3DNOW,SM
PI2FD     mmxreg,mmxreg       \2\x0F\x0F\110\01\x0D         PENT,3DNOW
PFNACC    mmxreg,mem          \301\2\x0F\x0F\110\01\x8A    
PENT,3DNOW,SM
PFNACC    mmxreg,mmxreg       \2\x0F\x0F\110\01\x8A         PENT,3DNOW
PFPNACC   mmxreg,mem          \301\2\x0F\x0F\110\01\x8E    
PENT,3DNOW,SM
PFPNACC   mmxreg,mmxreg       \2\x0F\x0F\110\01\x8E         PENT,3DNOW
PI2FW     mmxreg,mem          \301\2\x0F\x0F\110\01\x0C    
PENT,3DNOW,SM
PI2FW     mmxreg,mmxreg       \2\x0F\x0F\110\01\x0C         PENT,3DNOW
PF2IW     mmxreg,mem          \301\2\x0F\x0F\110\01\x1C    
PENT,3DNOW,SM
PF2IW     mmxreg,mmxreg       \2\x0F\x0F\110\01\x1C         PENT,3DNOW
PSWAPD    mmxreg,mem          \301\2\x0F\x0F\110\01\xBB    
PENT,3DNOW,SM
PSWAPD    mmxreg,mmxreg       \2\x0F\x0F\110\01\xBB        
PENT,3DNOW,SM
FFREEP    fpureg              \1\xDF\10\xC0                
PENT,3DNOW,FPU
--- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8 --- x8
--- x8 --- x8 ---


  sh...@ku...,
http://homepage1.nifty.com/herumi/gogo_e.html
----------------------------------------------------------------
Is this the same "0.98e3"?

How about that "RETFD" (was that it?) that got left out of 0.98? And
let's see, there's the "ADD" instruction...

Doc says:
"In the forms with an 8-bit immediate second operand and a longer first
operand, the second operand
is considered to be signed, and is sign-extended to the length of the
first operand. In these cases, the
BYTE qualifier is necessary to force NASM to generate this form of the
instruction."

Nasm now generates the "short form" automagicly, right?

I'm not volunteering to be the "Nasm Documentation Project", but I'll
try to help out a little if I can.

Best,
Frank