Execution model: Difference between revisions

Revision as of 04:14, 31 December 2016

Revision as of 13:52, 22 August 2017

Line 1:

{{Program execution}}

An '''execution model''' specifies how work takes place. Every programming language has an execution model, which is specified as part of the language specification, and is implemented as part of the language implementation. The details in the specification of an execution model cover things such as what is an indivisible unit of work, and what are the constraints on the order in which those units of work take place. For example, the addition operation is an indivisible unit of work in many languages, and in sequential languages such units of work are constrained to take place one after the other.

In particular, the [[C (programming language)|C programming language]], has a concept called a statement. The spec says that a statement is a chunk of syntax that is terminated by a ";". The language spec then says that execution of the program proceeds statement by statement, which tells us something about the execution model of the language. It tells us that statements are indivisible units of work and that they proceed in the same order as their syntactic appearance in the code (except when a control statement such as IF or WHILE modifies the order). By stating the order in which statements are executed, the language spec has stated constraints on the order of performing units of work. The C language actually has an additional level to its execution model, which is the order of precedence. It states the rules for the order of operations within a single statement. The order of precedence can be viewed as stating the constraints on performing the units of work that are within a single statement. So, ";" and "IF" and "WHILE" cover constraints on the order of statements, while order of precedence covers constraints on work within a statement. Hence, these parts of the C language specification are stating the execution model of the C language.

Execution models can also exist independently from programming languages, examples of which would be the [[POSIX Threads]] library, and Hadoop's Map-Reduce [[programming model]]. The implementation of an execution model can be via [[compiler]], or [[Interpreter_(computing)|interpreter]], and often includes a [[runtime system]].

An implementation of an execution model controls the order in which work takes place during execution. This order may be chosen ahead of time, in some situations, or it can be dynamically determined as the execution proceeds. Most execution models allow varying degrees of both. For example, the C language fixes the order of work within a statement and it fixes the order of all statements, except ones that involve an IF statement or a form of loop statement. Hence, most of the order of execution may be chosen statically, before execution begins, but a small portion must be chosen dynamically, as execution proceeds.

The static choices are most often implemented inside a [[compiler]], in which case the order of work is represented by the order in which instructions are placed into the executable binary. The dynamic choices would then be implemented inside the language's [[runtime system]]. The runtime system may be a library, which is called by instructions inserted by the [[compiler]], or the runtime system may be embedded into the [[executable]] directly, such as by inserting branch instructions, which make dynamic choices about which work to perform next.

However, an [[Interpreter_(computing)|interpreter]] may also be constructed for any language, in which case all decisions on order of execution are dynamic. An [[Interpreter_(computing)|interpreter]] can be viewed as being part translator, and part execution model implementation.

Each and every programming language has an execution model, which determines the manner in which the units of work (that are indicated by program [[Syntax (programming languages)|syntax]]) are [[Scheduling (computing)|scheduled]] for [[Execution (computing)|execution]]. Detailed examples of the specification of execution models of a few popular languages include those of Python,<ref>

<ref>{{cite web

| url = https://docs.python.org/3/reference/executionmodel.html

| title = Python Documentation: Execution Model

}}</ref>

the execution model of the Unified Parallel C (UPC) programming language,

<ref>{{cite web

| url = http://upc.lbl.gov/lang-overview.shtml

| title = UPC Language Features

}}</ref>

a discussion of various classes of execution model such as for imperative versus functional languages,<ref>

<ref>{{cite web

| url = https://books.google.com/books?id=4xwWNCiF9CgC&pg=PA61&lpg=PA61&dq=C+language+execution+model&source=bl&ots=pjBT99RWMQ&sig=bEKw6hgDsG9l4yqxiGyEEdFlWQI&hl=en&sa=X&ei=pElcVa-NNsbZsAWrs4DwDw&ved=0CFcQ6AEwCA#v=onepage&q=C%20language%20execution%20model&f=false

| title = Programming Languages and Execution Models

| author1=Cardoso, J.M.P.
| author2=Diniz, P.C.

| isbn=9780387096711

| year=2011

| publisher=Springer US

}}</ref>

and an article discussing execution models for real-time embedded languages.<ref>

<ref>{{cite web

| url = http://pertsserver.cs.uiuc.edu/~mcaccamo/papers/PREM_rtas11.pdf

| title = A Predictable Execution Model for COTS-based Embedded Systems

| date = 2011

| author1=PELLIZZONI, R.
| |author2=BETTI, E.
| |author3=BAK, S.
| |author4=YAO, G.
| |author5=CRISWELL, J.
| |author6=CACCAMO, M.
| author7= KEGLEY, R
| |last-author-amp=yes
| publisher = IEEE

| journal = Real-Time and Embedded Technology and Applications Symposium

| format = PDF

}}</ref>

== Overview ==

As a simple example of a basic execution model, that of the [[C (programming language)|C language]] is described in the book by Kernighan and Richie.<ref name="k&r1e">{{cite book | last=Kernighan | first=Brian W. | authorlink=Brian Kernighan | author2=Dennis M. Ritchie | title=The C Programming Language | edition=1st | publisher=[[Prentice Hall]] | date=February 1978 | ___location=[[Englewood Cliffs, NJ]] | isbn=0-13-110163-3 | authorlink2=Dennis M. Ritchie}}</ref> The book describes that work takes places in units called statements, which are syntactically indicated by a terminating ";". It specifies that statements are completed serially (one at a time) and sequentially (a previous statement completes before the next statement begins). Details such as this are part of the execution model.

As a simple example of a basic execution model, that of the [[C (programming language)|C language]] is described in the book by Kernighan and Richie.

<ref name="k&r1e">{{cite book | last = Kernighan | first = Brian W. | authorlink = Brian Kernighan |author2=Dennis M. Ritchie | title = The C Programming Language | edition = 1st | publisher = [[Prentice Hall]] | date = February 1978 | ___location = [[Englewood Cliffs, NJ]] | isbn = 0-13-110163-3 | authorlink2 = Dennis M. Ritchie }}</ref>

The book describes that work takes places in units called statements, which are syntactically indicated by a terminating ";". It specifies that statements are completed in order, one at a time, and a previous statement completes before the next statement begins. Details such as this are part of the execution model.

In the modern age, parallel programming is an increasingly important topic. Parallel execution models (several at a time) are much more complex. For example, the [[C++11]] standard includes sizeable wording that deals with the parallel execution model of the language.

== See also ==

{{Wiktionary|run-time}}

* [[Runtime system]]

* [[Execution (computing)]]