MB>
  >    New! Support for Intel MMX technology
  >    With support for the new Intel MMX technology, Watcom C/C++ 11.0
  >    allows you to take advantage of the latest architecture advances and
  >    enhance the performance of your multimedia and communications
  >    applications. You can develop lightning-fast applications that not
  >    only exploit the capabilities of the MMX instruction set, but also
  >    leverage the industry-leading optimization technology of Watcom C/C++.
  >    Plus, you get complete debugging support including the ability to
  >    single-step through your MMX instructions and view MMX registers in a
  >    separate window. And the functional interface from C/C++ makes it easy
  >    to generate in-line MMX instructions.
MB>

What a marvellous piece of puffery!  They sell the compiler on the basis
of all of this "new MMX technology" and make a fortune since they haven't
actually had to modify the compiler much at all.

After all, it's the _CPU_ that single-steps, not the debugger.  I'd be
amazed if any debugger could _not_ single-step over MMX instructions on an
MMX CPU.  They wouldn't display the correct mnemonics for the
instructions, of course, but I doubt that adding a new mnemonic to a table
somewhere in the debugger is really that hard.

Similarly for the viewing of the MMX registers.  The MMX registers are the
same as the FP registers.  The code to read/write them from/to the
debuggee thread and manipulate them was already there.  They probably just
had to change the window title and tweak the display format to 64-bit
instead of 80-bit.

The "in-line interface" was probably the hardest thing of the whole lot,
and they probably based that around `pragma aux'.

I bet that compiler marketing people adore Intel for inventing this MMX
lark.  (-:

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.01