about summary refs log tree commit diff homepage
diff options
context:
space:
mode:
authorCristian Cadar <cristic@cs.stanford.edu>2012-10-24 15:27:43 +0000
committerCristian Cadar <cristic@cs.stanford.edu>2012-10-24 15:27:43 +0000
commit4316936f20713742b1fdf9070505efbc9596ccb6 (patch)
tree7c62d9bfff52ba16efbcfba45e5793234f662358
parent648f3ed8e838976b14cf7452870bef4a56c9a6fe (diff)
downloadklee-4316936f20713742b1fdf9070505efbc9596ccb6.tar.gz
Patch by Jonathan Neuschäfer fixing inconsistency in Tutorial 1.
git-svn-id: https://llvm.org/svn/llvm-project/klee/trunk@166574 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--www/Tutorial-1.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/www/Tutorial-1.html b/www/Tutorial-1.html
index beb306e6..27d3c567 100644
--- a/www/Tutorial-1.html
+++ b/www/Tutorial-1.html
@@ -59,14 +59,14 @@
 
   KLEE operates on LLVM bitcode.  To run a program with KLEE, you
   first compile it to LLVM bitcode using <tt>llvm-gcc
-  --emit-llvm</tt>.  Assuming our code is stored in <tt>demo.c</tt>,
+  --emit-llvm</tt>.  Assuming our code is stored in <tt>get_sign.c</tt>,
   we run:
 
   <div class="instr">
   llvm-gcc --emit-llvm -c -g get_sign.c
   </div>
 
-  to generate the LLVM bitcode file <tt>demo.o</tt>.
+  to generate the LLVM bitcode file <tt>get_sign.o</tt>.
 
   It is useful to (1) build with <tt>-g</tt> to add debug information
   to the bitcode file, which we use to generate source line level