© 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis...
-
Upload
kerry-richard -
Category
Documents
-
view
230 -
download
3
Transcript of © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis...
![Page 1: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/1.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Program design and analysis
• Software components.• Representations of programs.• Assembly and linking.
1
![Page 2: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/2.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Software state machine
• State machine keeps internal state as a variable, changes state based on inputs.
• Uses:• control-dominated code;• reactive systems.
2
![Page 3: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/3.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
State machine example
idle
buzzer seated
belted
no seat/-
seat/timer on
no beltand notimer/-
no belt/timer on
belt/-belt/
buzzer off
Belt/buzzer on
no seat/-
no seat/buzzer off
3
![Page 4: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/4.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
C implementation#define IDLE 0#define SEATED 1#define BELTED 2#define BUZZER 3switch (state) {
case IDLE: if (seat) { state = SEATED; timer_on = TRUE; }break;
case SEATED: if (belt) state = BELTED;else if (timer) state = BUZZER;
break;…
}
4
![Page 5: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/5.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Signal processing and circular buffer
• Commonly used in signal processing:• new data constantly arrives;• each datum has a limited lifetime.
• Use a circular buffer to hold the data stream.
d1 d2 d3 d4 d5 d6 d7
time ttime t+1
5
![Page 6: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/6.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Circular buffer
x1 x2 x3 x4 x5 x6
t1 t2 t3
Data stream
x1 x2 x3 x4
Circular buffer
x5 x6 x7
6
![Page 7: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/7.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Circular buffers
• Indexes locate currently used data, current input data:
d1
d2
d3
d4
time t1
use
input d5
d2
d3
d4
time t1+1
use
input
7
![Page 8: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/8.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Circular buffer implementation: FIR filterint circ_buffer[N], circ_buffer_head = 0;int c[N]; /* coefficients */…int ibuf, ic;for (f=0, ibuff=circ_buff_head, ic=0;
ic<N; ibuff=(ibuff==N-1?0:ibuff++), ic++)f = f + c[ic]*circ_buffer[ibuf];
8
![Page 9: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/9.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Queues
• Elastic buffer: holds data that arrives irregularly.
9
![Page 10: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/10.jpg)
Buffer-based queues
#define Q_SIZE 32#define Q_MAX (Q_SIZE-1)int q[Q_MAX], head, tail;void initialize_queue() { head
= tail = 0; }void enqueue(int val) {
if (((tail+1)%Q_SIZE) == head) error();q[tail]=val;if (tail == Q_MAX) tail = 0; else tail++;
}
int dequeue() {int returnval;if (head == tail) error();returnval = q[head];if (head == Q_MAX) head = 0;
else head++;return returnval;
}
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed. 10
![Page 11: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/11.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Models of programs
• Source code is not a good representation for programs:• clumsy;• leaves much information implicit.
• Compilers derive intermediate representations to manipulate and optiize the program.
11
![Page 12: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/12.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Data flow graph
• DFG: data flow graph.• Does not represent control.• Models basic block: code with no
entry or exit.• Describes the minimal ordering
requirements on operations.
12
![Page 13: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/13.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Single assignment form
x = a + b;y = c - d;z = x * y;y = b + d;
original basic block
x = a + b;y = c - d;z = x * y;y1 = b + d;
single assignment form
13
![Page 14: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/14.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Data flow graph
x = a + b;y = c - d;z = x * y;y1 = b + d;
single assignment form
+ -
+*
DFG
a b c d
z
xy
y1
14
![Page 15: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/15.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
DFGs and partial orders
Partial order:• a+b, c-d; b+d x*yCan do pairs of
operations in any order.
+ -
+*
a b c d
z
xy
y1
15
![Page 16: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/16.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Control-data flow graph
• CDFG: represents control and data.• Uses data flow graphs as
components.• Two types of nodes:
• decision;• data flow.
16
![Page 17: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/17.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Data flow node
Encapsulates a data flow graph:
Write operations in basic block form for simplicity.
x = a + b;y = c + d
17
![Page 18: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/18.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Control
condT
F
Equivalent forms
valuev1
v2 v3
v4
18
![Page 19: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/19.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
CDFG example
if (cond1) bb1(); else bb2();bb3();switch (test1) {
case c1: bb4(); break;case c2: bb5(); break;case c3: bb6(); break;
}
cond1 bb1()
bb2()
bb3()
bb4()
test1
bb5() bb6()
T
F
c1
c2
c3
19
![Page 20: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/20.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
for loop
for (i=0; i<N; i++)loop_body();
for loop
i=0;while (i<N) {
loop_body(); i++; }equivalent
i<N
loop_body()
T
F
i=0
20
![Page 21: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/21.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Assembly and linking
• Last steps in compilation:
HLL compile assembly assembleHLLHLL assemblyassembly
linkexecutablelink
21
![Page 22: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/22.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Multiple-module programs
• Programs may be composed from several files.
• Addresses become more specific during processing:• relative addresses are measured
relative to the start of a module;• absolute addresses are measured
relative to the start of the CPU address space.
22
![Page 23: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/23.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Assemblers
• Major tasks:• generate binary for symbolic
instructions;• translate labels into addresses;• handle pseudo-ops (data, etc.).
• Generally one-to-one translation.• Assembly labels:
ORG 100label1 ADR r4,c
23
![Page 24: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/24.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Symbol table
ADD r0,r1,r2xx ADD r3,r4,r5
CMP r0,r3yy SUB r5,r6,r7
assembly code
xx 0x8yy 0x10
symbol table
24
![Page 25: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/25.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Symbol table generation
• Use program location counter (PLC) to determine address of each location.
• Scan program, keeping count of PLC.• Addresses are generated at
assembly time, not execution time.
25
![Page 26: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/26.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Symbol table example
ADD r0,r1,r2xx ADD r3,r4,r5
CMP r0,r3yy SUB r5,r6,r7
xx 0x8yy 0x10
PLC=0x7
PLC=0x7
PLC=0x7
PLC=0x7
26
![Page 27: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/27.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Two-pass assembly
• Pass 1:• generate symbol table
• Pass 2:• generate binary instructions
27
![Page 28: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/28.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Relative address generation
• Some label values may not be known at assembly time.
• Labels within the module may be kept in relative form.
• Must keep track of external labels---can’t generate full binary for instructions that use external labels.
28
![Page 29: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/29.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Pseudo-operations
• Pseudo-ops do not generate instructions:• ORG sets program location.• EQU generates symbol table entry
without advancing PLC.• Data statements define data blocks.
29
![Page 30: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/30.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Linking
• Combines several object modules into a single executable module.
• Jobs:• put modules in order;• resolve labels across modules.
30
![Page 31: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/31.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
external reference
entry point
Externals and entry points
xxx ADD r1,r2,r3B a
yyy %1
a ADR r4,yyyADD r3,r4,r5
31
![Page 32: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/32.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Module ordering
• Code modules must be placed in absolute positions in the memory space.
• Load map or linker flags control the order of modules.
module1
module2
module3
32
![Page 33: © 2008 Wayne Wolf Overheads for Computers as Components 2nd ed. Program design and analysis Software components. Representations of programs. Assembly.](https://reader036.fdocuments.in/reader036/viewer/2022081501/56649ecb5503460f94bd9aa2/html5/thumbnails/33.jpg)
© 2008 Wayne WolfOverheads for Computers as
Components 2nd ed.
Dynamic linking
• Some operating systems link modules dynamically at run time:• shares one copy of library among all
executing programs;• allows programs to be updated with
new versions of libraries.
33