| |
| | [No title] (Site not responding. Last check: 2007-10-27) |
 | | In early days of computing, when computer architects could not afford to use even a moderate volume of hardware, all operations were executed strongly sequentially, furthermore, each instruction and operation were split in smaller pieces, which also were executed sequentially, under the micro-program control. |
 | | Up to this point in the computer history, the compilers of software vendors could do resources scheduling (strictly sequential) at the time of compilation and, what is extremely important, this schedule was (and is) valid for all different models (with different technical characteristics of resources) of the same platform. |
 | | The same distributed binaries must be executed on many different computer models of the same platform, but for a multiple issue engine capable of parallel execution of different operations, a specific resource schedule should be substantially different for a different computer model with a different resource structure, unlike a single-issue engine. |
| edu.ioffe.ru /wmw/n1/babayan.html (5933 words) |
|