From 3a1cc630a10eabd9c0ee5fe4cc61e7df9b5ee37b Mon Sep 17 00:00:00 2001 From: Cristian Cadar Date: Thu, 8 Jun 2017 11:10:52 +0100 Subject: Fixed typos in comments related to vararg support. --- lib/Core/Executor.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'lib') 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: -- cgit 1.4.1