about summary refs log tree commit diff homepage
diff options
context:
space:
mode:
authorCristian Cadar <c.cadar@imperial.ac.uk>2017-06-08 11:10:52 +0100
committerCristian Cadar <c.cadar@imperial.ac.uk>2017-06-08 11:10:52 +0100
commit3a1cc630a10eabd9c0ee5fe4cc61e7df9b5ee37b (patch)
tree0dad8d935850b3b4ac04d830d1f83adb2d178ee9
parent4f5ea494986689dd89f97f9a64082527557c71c9 (diff)
downloadklee-3a1cc630a10eabd9c0ee5fe4cc61e7df9b5ee37b.tar.gz
Fixed typos in comments related to vararg support.
-rw-r--r--include/klee/ExecutionState.h2
-rw-r--r--lib/Core/Executor.cpp6
2 files changed, 4 insertions, 4 deletions
diff --git a/include/klee/ExecutionState.h b/include/klee/ExecutionState.h
index 32f840f6..78ebddac 100644
--- a/include/klee/ExecutionState.h
+++ b/include/klee/ExecutionState.h
@@ -51,7 +51,7 @@ struct StackFrame {
 
   // For vararg functions: arguments not passed via parameter are
   // stored (packed tightly) in a local (alloca) memory object. This
-  // is setup to match the way the front-end generates vaarg code (it
+  // is set up to match the way the front-end generates vaarg code (it
   // does not pass vaarg through as expected). VACopy is lowered inside
   // of intrinsic lowering.
   MemoryObject *varargs;
diff --git a/lib/Core/Executor.cpp b/lib/Core/Executor.cpp
index c5d294fb..8a445aa3 100644
--- a/lib/Core/Executor.cpp
+++ b/lib/Core/Executor.cpp
@@ -1289,7 +1289,7 @@ void Executor::executeCall(ExecutionState &state,
         return;
 
       // FIXME: This is really specific to the architecture, not the pointer
-      // size. This happens to work fir x86-32 and x86-64, however.
+      // size. This happens to work for x86-32 and x86-64, however.
       Expr::Width WordSize = Context::get().getPointerWidth();
       if (WordSize == Expr::Int32) {
         executeMemoryOperation(state, true, arguments[0], 
@@ -1297,7 +1297,7 @@ void Executor::executeCall(ExecutionState &state,
       } else {
         assert(WordSize == Expr::Int64 && "Unknown word size!");
 
-        // X86-64 has quite complicated calling convention. However,
+        // x86-64 has quite complicated calling convention. However,
         // instead of implementing it, we can do a simple hack: just
         // make a function believe that all varargs are on stack.
         executeMemoryOperation(state, true, arguments[0],
@@ -1321,7 +1321,7 @@ void Executor::executeCall(ExecutionState &state,
       // va_end is a noop for the interpreter.
       //
       // FIXME: We should validate that the target didn't do something bad
-      // with vaeend, however (like call it twice).
+      // with va_end, however (like call it twice).
       break;
         
     case Intrinsic::vacopy: