source: CIVL/README@ bddaf4c

1.23 2.0 main test-branch
Last change on this file since bddaf4c was 536af01, checked in by Stephen Siegel <siegel@…>, 11 years ago

Simplification of installation instructions in README and manual.

git-svn-id: svn://vsl.cis.udel.edu/civl/trunk@1793 fb995dde-84ed-4084-dfe6-e5aef3e2452c

  • Property mode set to 100644
File size: 11.3 KB
Line 
1 CIVL: The Concurrency Intermediate Verification Language
2 v0.15
3
4------------------------------ Overview -------------------------------
5
6CIVL is a framework encompassing...
7
8 * a programming language, CIVL-C, which adds to C a number of
9 concurrency primitives, as well as the ability to define
10 functions in any scope. Together, these features make for
11 a very expressive concurrent language that can faithfully
12 represent programs using various APIs and parallel languages,
13 such as MPI, OpenMP, CUDA, and Chapel. CIVL-C also provides
14 a number of primitives supporting verification.
15 * a model checker which uses symbolic execution to verify a
16 number of safety properties of CIVL-C programs. The model
17 checker can also be used to verify that two CIVL-C programs
18 are functionally equivalent.
19 * a number of translators from various commonly-used languages
20 and APIs to CIVL-C. (This part is still a work in progress.)
21
22CIVL is developed by the Verified Software Laboratory at the
23University of Delaware Department of Computer Science.
24For more information, visit http://vsl.cis.udel.edu/civl
25
26Developers:
27
28Matthew B. Dwyer
29Ziqing Luo
30Michael Rogers
31Stephen F. Siegel
32Manchun Zheng
33Timothy K. Zirkel
34
35------------------------------- License -------------------------------
36
37CIVL is open source software distributed under the GNU
38General Public License. However, the libraries used by CIVL
39(and incorporated into the complete distribution) use various
40licenses. See directory licenses for the license of each component.
41
42-------------------------- Updates from v 0.14 -------------------------
43
441. Fixed the bug that erroneously checking mpi processes statuses inside communicators
45
462. Fixed the bug that invalid command line inputs crash CIVL.
47
483. Fixed the bug that CIVL mis-handling float-to-int conversion.
49
504. Fixed the bug that Translation will ignore unused variable erroneously.
51
525. Fixed the bug that CIVL implementation misses extents information for literal array assignments.
53
546. Fixed the bug that CIVL didn't report array out of bound error.
55
567. Fixed performance bug dealing with MPI/link.
57
588. Fixed the bug that POR didn't recognize input array.
59
609. Fixed the bug that ABC can't print $forall.
61
6210. Fixed the bug of linkage with bound variables.
63
6411. Improving CIVL by get rid of unnecessary statements enabled from a nondeterministic statement.
65
6612. Support compound literals for input variables.
67
6813. Improves the performance of SARL which also makes CIVL run faster.
69
7014. Makes sources of inserted texts by transformer more clear.
71
7215. Support time.h
73
7416. Implemented fflush()
75
7617. Extended ABC to handle Cuda-c extensions.
77
7818. Simplify array representation in SARL.
79
80
81
82------------------------- Binary Installation -------------------------
83
84For most users, this will be the easiest way to install and
85use CIVL. Developers should instead follow the instructions for
86"Source Installation" below.
87
881. Install at least one of the theorem provers below.
89The more provers you install, the more precise CIVL analysis will
90be. Note that CIVL only requires the binary executable
91version of each prover; you can ignore the libraries, various
92API bindings, etc. You just need to ensure that
93each binary executable is in your PATH when you run
94"civl config". The currently supported provers are:
95
96 - CVC3, http://www.cs.nyu.edu/acsys/cvc3/download.html
97 download the latest, optimized build with static library
98 and executable for your OS. Place the executable file
99 "cvc3" in your PATH. You can discard everything else.
100 Alternatively, on some linux systems, CVC3 can be installed
101 using the package manager via "sudo apt-get install cvc3".
102 This will place cvc3 in /usr/bin.
103
104 - CVC4, http://cvc4.cs.nyu.edu/downloads/
105
106 - Z3, http://z3.codeplex.com/SourceControl/latest
107
1082. Install a Java 7 SDK if you have not already. Go to
109
110 http://www.oracle.com/technetwork/java/javase/downloads/
111
112for the latest from Oracle. On linux, you can instead use
113the package manager:
114
115 sudo apt-get install openjdk-7-jdk
116
1173. Download the CIVL distribution from http://vsl.cis.udel.edu/civl.
118
1194. Unzip and untar the CIVL distribution file if this
120does not happen automatically. This should result in a
121folder named CIVL-TAG, where TAG is some version ID string.
122This folder contains the following:
123
124 - README : this file
125 - bin : containing one executable sh script called "civl"
126 - lib : containing civl-TAG.jar
127 - doc : containing the manual and the tutorial of CIVL
128 - emacs : CIVL-C emacs mode and its installation instructions
129 - licenses : licenses for CIVL and included libraries
130 - examples : some example CIVL programs
131
1325. You can move the CIVL folder wherever you want.
133The JAR file in the lib directory is all you need to run CIVL.
134You may also move this jar file wherever you want. You
135run CIVL by typing a command that begins
136"java -jar /path/to/civl-TAG.jar ...". For convenience
137you may instead use the shell script "civl" in bin,
138which allows you to replace "java -jar /path/to/civl-TAG.jar"
139with just "civl" on the command line. Simply edit the civl script
140to reflect the path to civl-TAG.jar and place the script
141somewhere in your PATH. Alternatively, you can just define
142an alias in your .profile, .bash_profile, or equivalent, such as
143
144alias civl='java -jar /path/to/civl-TAG.jar'
145
146In the following, we will assume that you have defined
147a command "civl" in one these ways.
148
1496. Type "civl config". This should report that it found
150the theorem provers you installed (and are in your PATH).
151It should create a file called ".sarl" in your home directory
152which you can also edit by hand.
153
154
155------------------------- Source Installation -------------------------
156
157We recommend using the Eclipse IDE for Java/EE developers.
158
1590. Install theorem provers following the directions above.
160Install Eclipse IDE for Java/EE developers if you have not already
161done so.
162
1631. Install an SVN plugin in Eclipse (such as Subversive) if you have
164 not already.
165
1662. Install prerequisite projects ABC, SARL and GMC.
167 Make sure that the three projects are put in the workspace
168 directory where CIVL will be created. Specifically:
169
170 a. Install the symbolic algebra and reasoning library SARL.
171 In Eclipse, select New Project...from SVN, use the archive
172 svn://vsl.cis.udel.edu/sarl. After entering that, open it
173 up and select the "trunk". After checking out trunk, name
174 the project "SARL". Then follow the instructions in the INSTALL
175 file for Eclipse installation. Build the sarl.jar from within
176 Eclipse by right-clicking (or ctrl-clicking) on the build.xml
177 file and selecting Run As->Ant Build.
178
179 b. Install the C front-end ABC. In Eclipse,
180 select New Project...from SVN, use the archive
181 svn://vsl.cis.udel.edu/abc. After entering that, open it
182 up and select the "trunk". After checking out trunk, name
183 the project "ABC". Then follow the instructions in the INSTALL
184 file for Eclipse installation. Build the abc.jar from within
185 Eclipse by right-clicking (or ctrl-clicking on OS X) on the
186 build.xml file and selecting Run As->Ant Build.
187
188 c. Install the generic model checking utilities package GMC.
189 In Eclipse, select New Project...from SVN, use the archive
190 svn://vsl.cis.udel.edu/gmc. After entering that, open it
191 up and select the "trunk". After checking out trunk, name
192 the project "GMC". Build the gmc.jar from within Eclipse
193 by right-clicking (or ctrl-clicking) on the build.xml file and
194 selecting Run As->Ant Build.
195
1963. From within Eclipse, select New Project...from SVN. The archive is
197 svn://vsl.cis.udel.edu/civl. After entering that, open it up and
198 select the "trunk". (It is simplest to just check out the trunk for
199 the Eclipse project.)
200
2014. Check out the trunk, and create the project using the New Java
202 Project Wizard as usual, naming it "CIVL". The .project, .classpath,
203 and other Eclipse meta-data are already in the SVN archive,
204 saving you a bunch of work.
205
2065. If you already have the VSL dependencies library, you may
207 skip this step. Otherwise, download the tgz archive of VSL
208 dependencies from http://vsl.cis.udel.edu/tools/vsl_depend
209 Unzip the .tgz file and you will have the folder vsl.
210 Move vsl to /opt.
211 Note: you probably will need to use sudo for this.
212 Also, if you don't already have a directory called /opt,
213 you will have to create it with "mkdir /opt". Also, if you
214 don't want to use /opt for some reason, you can use any
215 directory you want; just modify the instructions below
216 accordingly.
217
218 Suppose that you put the .tgz file (or .tar file if your browser
219 unzipped it automatically to a .tar file) in the directory DOWNLOAD.
220 You can use the following commands:
221
222 $ cd DOWNLOAD
223 $ tar xzf YourTgzOrTarFile vsl
224 $ sudo mv vsl /opt
225
226 (Leave out the "x" in the tar command if the file was already
227 unzipped.) Now you can type "ls /opt/vsl", and the output
228 should be
229
230 README.txt lib licenses src
231
2326. If default_build.properties matches the configuration of your system,
233 then you can skip this step. Otherwise, you may need to create a file
234 build.properties in the directory containing build.xml.
235 Copy and paste the content from any file under properties, edit each
236 entry with the path configured in your system. The newly created file
237 build.properties will automatically be used by ant to to build the
238 .jar file.
239
2407. Navigate to Preferences -> Java -> Build Path -> ClassPath
241 Variables, and then select New to create a classpath variable VSL,
242 and specify its value to be /opt/vsl.
243
2448. Do a clean build. Everything should compile. Generate the civl.jar
245 by right-clicking (or ctrl-click on OS X) the build.xml file and
246 Run As->Ant Build.
247
2489. Somewhere on your system, create a plain text file containing
249 exactly the following two lines:
250
251#!/bin/sh
252java -jar /Path/To/Your/workspace/CIVL/civl.jar $@
253
254 where "/Path/To/Your/workspace" is replaced with the path
255 to your Eclipse workspace directory. Name this file "civl",
256 put it in your PATH, and make it executable (chmod ugo+x civl).
257 Alternatively, you can define an alias in your .profile,
258 .bash_profile, .bashrc, or equivalent:
259
260alias civl='java -jar /Path/To/Your/workspace/CIVL/civl.jar'
261
26210. From a terminal window, execute "civl config". This should
263 find the theorem provers in your PATH and create a file
264 .sarl in your home directory.
265
26611. In Eclipse, navigate to "Run->Run Configurations... Create a new
267 JUnit configuration."
268 Name it "CIVL Regression Tests". Select "Run all tests in the
269 selected project..." and navigate to the folder "test/regress"
270 in the CIVL project. The Test runner should be JUnit 4. Under the
271 Arguments tab, type "-ea" (without the quotes) in the VM arguments
272 area (to enable assertion checking).
273
27412. An example of how to set up a single test from within Eclipse:
275 create a new Run Configuration via the Run->Run
276 Configurations... menu. Create a new "Java Application"
277 configuration. Call it "CIVL barrier2". The Project is CIVL. The
278 main class is edu.udel.cis.vsl.civl.CIVL. Under the Arguments tab,
279 set the Program arguments to
280
281 verify examples/concurrency/barrier2.cvl
282
283 Modify the VM arguments as in the step above. You should now be
284 able to run the test by clicking "Run".
285
Note: See TracBrowser for help on using the repository browser.