> Some millicode instructions will outperform their PoOp-code > counterparts > because millicode has access to hardware features not available to > ordinary code. For example, MVCL(E) has the ability to move data > under > certain conditions without loading it into cache. (You can't do that > with looping MVC.) Millicode routines also have access to the MVCX > instruction which performs a variable-length MVC -- something > ordinary > programs cannot do without using the EXecute instruction.
MVCX sounds like it would be usefull for non-millicode, any idea why it was not externalized? Is there a coresponding CLCX? -- Richard
