|AS/400 (was: Debugging of optimized code) SAND_DUANE@tandem.com (1995-01-31)|
|Re: AS/400 (was: Debugging of optimized code) email@example.com (1995-02-01)|
|Re: AS/400 (was: Debugging of optimized code) firstname.lastname@example.org (1995-02-04)|
|Keywords:||architecture, optimize, debug|
|Organization:||America Online, Inc. (1-800-827-6364)|
|Date:||Sat, 4 Feb 1995 03:18:53 GMT|
|Received-Date:||Fri, 3 Feb 1995 22:18:55 -0500|
The instruction sets of the AS/400 are deliberately a mystery. Can
anyone sketch for us the nature of the generic instruction set and one
or more of the existing actual instruction sets? And how about the
performance and methods of the load-time translators?
There are two of these artificial instruction sets. The newer one,
designed for languages like C, is a stack-based notation similar to P-code
or U-code in basic concept (though with many significant differences).
The older one, designed for languages like RPG and older versions of
COBOL, it a 3-address storage-to-storage notation (a pain to optimize
well, hence the need for the newer version).
Maybe AS/400 users will finally see a 'full
optimizations with little or no debugging' switch.
There are indeed several options for optimization, each with decreasing
levels of debugability. At the highest level, debugging is pretty much
catch as catch can, but every effort is made to allow as much debugability
as possible without impacting optimization.
Return to the
Search the comp.compilers archives again.