search for: gvtop

Displaying 4 results from an estimated 4 matches for "gvtop".

Did you mean: vtop
2006 May 18
1
[LLVMdev] Runtime optimisation in the JIT
...with the existing infrastructure, to do adaptive compilation using the JIT interpreter? Watching said interpreter through GDB shows that it starts off with runFunction() called on the function representing "main", and ends up at the line: rv.IntVal = PF(ArgValues[0].IntVal, (char **)GVTOP(ArgValues[1])); where PF is a pointer to (I think) the machine code representation of main(). So, main() is invoked, and the result returned to the caller. Now, what I'm looking at implementing is something like the following scenario. a. The JIT interpreter starts executing the program. b...
2004 Oct 07
2
[LLVMdev] problem with lli (llvm 1.3)
...------ However, if the program doesn't do anything (i.e., an empty main() function). The lli won't crash. I traced lli using gdb, and found that it crashes within JIT::runFunction(). In particular, the problem is in line 70 of JIT.cpp: int ExitCode = PF(ArgValues[0].IntVal, (char **) GVTOP (ArgValues[1]), (const char **) GVTOP (ArgValues[2])); Is anybody having any idea about this? Thanks a lot. Shukang Zhou
2019 Jul 17
2
Help to understand LoadValueFromMemory
...inter to the buffer where fread stored the data - %5 in my case ) and the fread() has been already called. I thought the correct approach to achieve what I need was: ExecutionContext& SF = ECStack.back(); GenericValue SRC = getOperandValue(source, SF); GenericValue* Ptr = (GenericValue*)GVTOP(SRC); GenericValue Result; source->getPointerOperand()->getType()->dump(); //[40 x i8]* LoadValueFromMemory(Result, Ptr, source->getPointerOperand()->getType()); and use Result.PointerVal ... In the end I have the first 4 bytes within Result.PointrVal but I cannot see the othe...
2008 Jun 19
1
[LLVMdev] Constant function pointers and inlining
Hello, I've been working on turning PHP scripts into LLVM IR and I've gotten to the stage where I'm able to construct LLVM code that calls the PHP opcode handlers that I've pre-compiled to LLVM IR in the correct order. However, the PHP API is designed so that the handlers are not globally accessible (qualified by "static" in the C source). Instead they're supposed to