-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
186 lines (124 loc) · 5.74 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
#
# Pluto README
#
# Uday Bondhugula
#
LICENSE
Pluto is available under GPL v3, and libpluto is available under LGPL v2.1.
INSTALLING PLUTO
Requirements: A Linux distribution. Pluto has been tested on x86 and
x86-64 machines running Fedora Core {4,5,7,8,9}, Ubuntu, and RedHat
Enterprise Server 5.x. Solaris should also be fine if you have GNU
utilities. In order to use the development version from Pluto's git
repository, automatic build system tools including autoconf, automake,
and libtool are needed. GMP (GNU multi precision arithmetic library) is
needed by ISL (one of the included libraries). If it's not already on
your system, it can be installed easily with, for eg.,
'sudo yum -y install gmp gmp-devel' on a Fedora, or
'sudo apt-get install libgmp3-dev' on an Ubuntu.
Pluto includes all libraries that it depends on. autoconf/automake
system will take care of automatically building everything. Nothing else
needs to be downloaded and installed separately.
BUILDING PLUTO
Stable release
$ tar zxvf pluto-0.9.0.tar.gz
$ cd pluto-0.9.0/
$ ./configure [--enable-debug] [--with-isl-prefix=<isl install location>]
$ make
$ make test
Development version from Git
$ git clone git://repo.or.cz/pluto.git
$ cd pluto/
$ git submodule init
$ git submodule update
$ ./bootstrap.sh
$ ./configure [--enable-debug] [--with-isl-prefix=<isl install location>]
$ make
$ make test
* --with-isl-prefix=<location> to compile and link with an already installed
isl. By default, the version of isl bundled with Pluto will be used.
If you do not have ICC, uncomment line 7 and comment line 8 of
examples/common.mk.
'polycc' is the wrapper script around src/pluto (core transformer) and
all other components. 'polycc' runs all of these in sequence on an input
C program (with the section to parallelize/optimize marked) and is what
a user should use on input. Output generated is OpenMP parallel C code
that can be readily compiled and run on shared-memory parallel machines like
general-purpose multicores. libpluto.{so,a} is also built and can be found
in src/.libs/. 'make install' will install it.
TRYING A NEW CODE
- Use '#pragma scop' and '#pragma endscop' around the section of code
you want to parallelize/optimize.
- Then, just run
./polycc <C source file> --parallel --tile
The transformation is also printed out, and test.par.c will have the
parallelized code. If you want to see intermediate files, like the
.cloog file generated (.opt.cloog, .tiled.cloog, or .par.cloog
depending on command-line options provided), use --debug on command
line.
- Tile sizes can be specified in a file 'tile.sizes', otherwise default
sizes will be set. See doc/DOC.txt on how to specify the sizes.
To run a good number of experiments on a code, it is best to use the
setup created for example codes in the examples/ directory
- Just copy one of the sample directories, edit Makefile (SRC = ),
util.h, decls.h appropriately (put your problem size declarations in
decls.h)
- Now, do a make (this will build all executables; 'orig' is the
original code, 'tiled' is the tiled code, 'par' is the OpenMP
parallelized+locality optimized code; 'par2d' is with two degrees of
parallelism whenever it exists). One could do 'make <target>', where
target can be orig, orig_par, opt, tiled, tiled_par
- 'make test' to test for correctness
COMMAND-LINE OPTIONS
Run
./polycc -h
or see documentation (doc/DOC.txt) for details
TRYING ANY INCLUDED EXAMPLE CODE
Let us say we are trying the 2-d Gauss Seidel. Do a 'make par', this
will generate seidel.par.c from seidel.c and also compile it to generate
'par'. Likewise, 'make tiled' for 'tiled' and 'make orig' for the
'orig'.
$ cd examples/seidel
seidel.orig.c: This is the original code (the kernel in this code is
extracted)
seidel.opt.c: This is the transformed code without tiling (this is not
of much use, except for seeing the benefits of fusion in some cases)
seidel.tiled.c: This the pluto tiled code (not parallelized) generated
from the tool - this should be used for single core execution
seidel.par.c: This is the pluto parallelized + locality tiled code. This
has OpenMP pragmas and the code is L1 tiled or L1 and L2 tiled.
seidel.par2d.c: In this case, since we have two degrees of pipelined
parallelism, so the .par2d.c is the code with nested parallel OpenMP
pragmas.
- To change any of the flags used for an example, edit the top section
of examples/common.mk or the Makefile in the example directory
- To manually specify tile sizes, create tile.sizes; see
examples/matmul/ for example or doc/DOC.txt for more information.
- orig (orig_par is the icc auto-parallelized original code), tiled, par
and par2d are corresponding executables; they already have timers; you
just have to run them and that will print execution time as well
So, to run pluto parallelized version:
$ export OMP_NUM_THREADS=4; ./par
To run ICC auto-parallelized version:
$ export OMP_NUM_THREADS=4; ./orig_par
To run the original unparallelized code (compiled with icc -fast)
$ ./orig
To run the pluto tiled version (non-parallelized, local tiled)
$ ./tiled
- 'make clean' in the particular example's directory removes all the
executables as well as the generated codes
To launch a complete verification that compares output of tiled, par
with orig for all examples, in the examples/ directory, run
[examples/ ]$ make test
MORE INFO
* See doc/DOC.txt for an overview of the system and details on all
command-line options.
* For specifying custom tile sizes through 'tile.sizes' file, see
doc/DOC.txt
* For specifying custom fusion structure through '.fst' file, see
doc/DOC.txt
CONTACT
Please send all bugs reports and comments to
Uday <[email protected]>