|
Steve Richter wrote: ... Also, is w-code more optimizable than MI code, and if so, why ? W-Code is MUCH more optimizable, for at least two key reasons. First, it's expression-based instead of storage-based. That is, results are viewed as being returned to a logical (not necessarily physical) stack, not to the storage location specified as an operand on the instruction. Secondly, the exception handling semantics are very different. One example: in W-Code there is no concept of handling an exception by transferring control to the "next" MI (or W-Code) instruction. That ability in the original MI severely inhibits optimization because in some respects every instruction becomes a potential control flow target. Paul Godtland
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.