# Relational Semantics of a Simple Language

We will next give meaning (semantics) for our Simple Programming Language using relations between initial and final state of each command. We illustrate the use of this semantics by showing certain very simple program equivalence properties.

When we write “x” we mean the variable named x viewed as a syntactic object (string or a node in syntax tree). We sometimes omit quotes.

## Examples of Semantics for Some Programs

In such a semantics, if the state of the program is given by one integer variable *x*, then the meaning of this 'increment program':

x = x + 3; x = x - 2

is the relation .

A pair of integers is in relation, written , if and only if . Using set comprehensions, we write

The meaning of

x = x + x

is

The meaning of

while (true) { }

is empty relation.

#### Why Relations

The meaning is, in general, an arbitrary *relation*. Therefore:

- For certain states there will be no results. In particular, if a computation starting at a state does not terminate, then for no will there be a state of the form in the relation.
- For certain states there will be multiple results, when and for . Intuitively, this means command execution starting in will sometimes compute and sometimes . Verification of such program must account for both possibilities.
- Multiple results are important for modelling e.g. concurrency, as well as approximating behavior that we do not know (e.g. what the operating system or environment will do, or what the result of complex computation is)

## Program States, Relations on States

Our programs can have any finite number of integer variables. Let denote the set of variable names such as 'x' in the example above. The state of our program is a function mapping variable names to their values, and the set of states

is the set of all such functions. We assume that the range of variables is (the set of integers), but most of what we say will be independent on whether the variables are integers or have some other type.

In the above increment program, and a state is of the form for some integer (recall that we represent each function as relation ). So the increment function is given by a relation, call it , that takes the state and maps it to state :

What happens when we have more than one variable? Let and consider this program:

x = y + y

The meaning of this program is given by relation

Renaming variables so the initial value of variable “x” is denoted and final value denoted , we have

I will call the relation *r* the *relational semantics* of this command and the formula the *formula semantics* of this command.

When we have multiple variables, we can give semantics to assignment statements using function update notation. Regardless of the number of variables in , the relational semantics of *x=y+y;* is

## Semantic Functions

Let denote the set of all commands (programs). Our goal is to define semantic function for commands, denoted (**r**elation of the **c**ommand), which maps each command into its relational semantics . Formally,

To define meaning of statements such as *x=y+y;* we need a way to evaluate a term such as *y+y* in a given state. We introduce function (**f**unction of the **t**erm), which maps a term into a function from states to values:

## Meaning of Assignment

Given some definition of , the meaning of the assignment statement is simply

## Meaning of Terms

We next define meaning of terms, whose syntax we defined earlier.

T ::= K | V | (T + T) | (T - T) | (K * T) | (T / K) | (T % K) F ::= (T=T) | (T < T) | (T > T) | (~F) | (F & F) | (F|F) V ::= x | y | z | ... K ::= 0 | 1 | 2 | ...

The recursive definition corresponds to a program you would write in e.g. Scala to compute the value of an expression in a given state when writing an interpreter.

Based on that context-free grammar, we can define recursively the terms semantic :

## Sequential Composition as Relation Composition

To execute a statement sequence, we execute the first statement and from the resulting state execute the second statement. We therefore define statement sequential composition as relation composition of statement meanings:

### Example: commuting assignments

Consider the task of a programmer or a compiler who wishes to reorder two assignment statements, converting

x = e1; y = e2

into

y = e2; x = e1

where and . Under what conditions will these two program fragments have the same meaning?

To answer that question, we just have to derive these two expressions :

Symetrically, we have:

Thus, if y is free in and x is free in , these two fragments will have the same meaning.

## Towards Assume: Some Intuition about Control Flow Graphs

How do we represent if-then-else statements and loops using flow charts and control-flow graphs?

We next look at the constructs that allow us to do such representation (for structured commands) using the terminology of relations.

## Assume Statement

Assume statement is a useful declarative statement, which we will use to define the meaning of several remaining commands. The meaning of *assume* is simply is the diagonal relation, which produces no resulting states if the given expression is false, and does nothing if the expression is true:

where .

## Non-deterministic Choice as Union

Non-deterministic choice is another useful declarative statement, which non-deterministically chooses to execute one of the two statements. We use it to express other statements, as well as to model branching with conditions that we cannot express in the language. Its meaning is simply union of relations:

## Representing if-then-else Using Non-Deterministic Choice and Assume

We will define the semantics of

if (F) then c1 else c2

as the semantics of

(assume(F); c1) [] (assume(~F); c2)

Note that we are using non-deterministic choice, but exactly one of the two statements in the non-determinitic choice will succeed.

### Exercise: expanding the definition of conditionals

We can also express this semantics directly as:

## Non-deterministic Loop as Transitive Closure

Just as we use non-deterministic choice (union) to represent conditional statment, we use non-deterministic loop statement (transitive closure) to represent while loops. A statement *loop( c )* executes statement *c* any number of times, possibly zero. Its meaning is transitive closure of the meaning of *c*.

## Expressing While using Non-deterministic Loop

We define semantics of

while(F) c

as the semantics of

loop (assume(F);c); assume(~F)

Why does this definition make sense? It will be union of relations of the form:

(assume(F); c)^n assume(~F)

for all n. But if the value of n is wrong the result will be empty relation:

- if it executes even if F is false, then assume(F) will give empty relation
- if it stops even if F is true, then assume(~F) at the end will give empty relation

Therefore, the result is equal to the correct number of execution times.

## Summary of Simplifying the Language

Instead of

c ::= x=T | (if (F) c else c) | c ; c | (while (F) c)

we can have language

c ::= x=T | assume(F) | c [] c | c ; c | loop c

Applying it to a multiplication example we obtain

r = 0; i = y; loop ( assume (i > 0); r = r + x; i = i - 1 ); assume (i <= 0);

## Havoc Statement

Havoc statement is another useful declarative statement. It changes a given variable entirely arbitrarily: there will be one possible state for each possible value of integer variable.

### Expressing Assignment with Havoc+Assume

We can prove that the following equality holds under certain conditions:

In other words, assigning a variable is the same as changing it arbitrarily and then assuming that it has the right value. Under what condition does this equality hold?

## Further reading

- C A R Hoare and He Jifeng. Unifying Theories of Programming. Prentice Hall, 1998
- Semantics-based Program Analysis via Symbolic Composition of Transfer Relations, PhD dissertation by Christopher Colby, 1996