I noticed a few things since I started this thread. First off, the version of MASM discussed above is 6.15. Also, it may be that those MASM options required to replicate the object file from an asm listing that was produced by a CVF compile-link of Fortran source code differ from the options a user would use in writing an assembly program from scratch. Another MASM switch that may be important is -Zp4 (to align structures along 4-byte boundaries). Also, one of the reasons I wanted to re-assemble an asm listing was to generate timings for each assembly instruction (not given in the CVF asm listings); this requires the -Sc switch.
So here is what I think should be a good set of switches to compile assembly language code into an CVF-compatible object file (especially if you are trying to get an insight into exactly how your Fortran code compiled from the CVF asm listing):
ML.EXE -I. -Zm -Cp -Fl -Sa -Sc -coff -Zp4 -c asmlistingfile.asm
One more thing, even with older assembler versions one can always embed the newer processor instructions by directly embedding op codes using the "DB" (define byte command). For example to encode a CPUID instruction insert the two lines: "db 0fh" then "db 0a2h" (see Intel documentation AP-485 on this particular example and on the CPUID instruction in general).
