Add a comment: don't expect from external function resolver in interpreter
authorAnton Korobeynikov <asl@math.spbu.ru>
Mon, 30 Jul 2007 23:03:25 +0000 (23:03 +0000)
committerAnton Korobeynikov <asl@math.spbu.ru>
Mon, 30 Jul 2007 23:03:25 +0000 (23:03 +0000)
things, it wasn't designed to handle.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@40608 91177308-0d34-0410-b5e6-96231b3b80d8

lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp

index 55391df888696a929f977c5f93cd4c78d76c639e..e86c1bc2b4530e274527199b002c50607d953747 100644 (file)
@@ -62,6 +62,11 @@ static char getTypeID(const Type *Ty) {
   }
 }
 
+// Try to find address of external function given a Function object.
+// Please note, that interpreter doesn't know how to assemble a
+// real call in general case (this is JIT job), that's why it assumes,
+// that all external functions has the same (and pretty "general") signature.
+// The typical example of such functions are "lle_X_" ones.
 static ExFunc lookupFunction(const Function *F) {
   // Function not found, look it up... start by figuring out what the
   // composite function name should be.