There was no High Level Language! Most of the S/360 instruction times were based on 'Frame Intervals' on what you could do in a given amount of time or instructions. The Saturn/Apollo used this in a n-way voting scheme to achieve predictable results in a given window. Many of the concepts are carried over in our single processor multi-core hardware. Parallel instructions, results comparison, and instruction retry.
In a message dated 3/7/2019 1:56:17 PM Central Standard Time, [email protected] writes: Then, as has been discussed here a number of times, if you want the best code possible for a given processor generation, use a high-level language (typically C) and tell the compiler what machine you will be running on. People with both great experience and access to IBM information that you and I don't have design and configure the code generation in the IBM compilers, and it's almost a sure bet that it'll ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
