C-3. Outline of working plan

While issue study and experiement will be the primary nature of our work, we propose the following system architecture and execution mechanism as a target for identifying the issues in optimal intergration of interpretation and compilation/execution technologies.

• a front processor converts the application program into some intermediate form, and performs certain analysis, and possible restructuring, in addition to syntax and semantics checking. The result will be a partially ordered set of interpretive frames. Note we use the term front processor instead of front-end, since it is supposed to do more work than typical compiler front-end.
• The actions specified in a frame may be performed in one of the three ways.
  • Executed by an interpreter directly.
  • Some precompiled computational library function is invoked locally to accomplish the task; this function may be executed sequentially or in parallel.
  • The frame is sent to some registered remote system, which will get the work done, once again either sequentially or in parallel at its capacity.
• Necessary dataflow coordination must be observed.
• Do not encourage fine grain communication among local processor and remote processor.
• Relation between the interpretive frames and source code is well documented internally for diagnositic and debugging purpose.

The distinction between local processor and registered remote system would be application dependent, a machine on the same local area network may be considered local or remote for different situations. An architecture overview of the perspective system is sketched as in Figure .

  
Figure: Architecture overview of a target system

In what follows, we'll give a brief introduction to each of the components in the system.

• Language front-end
• Program analyzer
• Interpretive frame generator
• Coordinating interface
• Resource Managemant
• Task Migration
• Fault Tolerance