search for: argvec

> Args needs to be an array of the arguments and NumArgs needs to be the > size of the array. If you have a std::vector then you can just: > > new CallInst(F, &ArgVec[0], ArgVec.size(), ...) Doesn't the code above make an assumption about how std::vector is implemented? If ArgVec is defined as std::vector<Value*> ArgVec; then &ArgVec[0] returns a Value**. Let us define Value** Params = &ArgVec[0]; The constructor for CallInst accesses P...

...bwendling:llvm-eh] svn diff gcc/config/linux.h Index: gcc/config/linux.h =================================================================== --- gcc/config/linux.h (revision 41554) +++ gcc/config/linux.h (working copy) @@ -113,8 +113,9 @@ if (flag_pic) \ argvec.push_back ("--relocation-model=pic"); \ else \ - argvec.push_back ("--relocation-model=static"); - + argvec.push_back ("--relocation-model=static"); \ + if (flag_exceptions) \ +...

...ygen/classes.html and look there for help on the new API. It is regenerated every night so it should be perpetually up to date with CVS HEAD. Args needs to be an array of the arguments and NumArgs needs to be the size of the array. If you have a std::vector then you can just: new CallInst(F, &ArgVec[0], ArgVec.size(), ...) Reid. > > Thanks, > Ryan > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

To create a new CallInst I used to call the following constructor: CallInst(Value *F, const std::vector<Value*> &Par, const std::string &Name = "", Instruction *InsertBefore = 0); However, it seems as though that constructor has been removed. I assume that I'm suppossed to use the following constructor, but I can't figure out what to pass as the Args parameter

Chris Lattner wrote: > On Dec 1, 2011, at 5:23 PM, Nick Lewycky wrote: >>> Instead of adding a bunch of instance variables (+ getters/setters) into TargetMachine, why not make TargetOptions be a class, and have TM contain an instance of it? >> >> That works too, it makes little difference to me. One reason is that >> most references to these globals are inside classes

...r help on the new > API. It is regenerated every night so it should be perpetually up to > date with CVS HEAD. > > Args needs to be an array of the arguments and NumArgs needs to be the > size of the array. If you have a std::vector then you can just: > > new CallInst(F, &ArgVec[0], ArgVec.size(), ...) > > Reid. > >> Thanks, >> Ryan >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/ll...

...rds. I am using clang to compile a C++ module, and an ExecutionEngine (MCJIT) to execute a function it defines. That works (or pretends to). However, if I call the module's constructors first: exec_engine->runStaticConstructorsDestructors(false); exec_engine->runFunctionAsMain(function, argvec, NULL); execution still works, but my program crashes when it exits, in __run_exit_handlers(). I can't tell from gdb what exit handler is crashing, but no calls are made to atexit() or on_exit(); all exit handlers are installed via __cxa_atexit(). This may or may not be meaningful, but I am f...

...module, and an ExecutionEngine (MCJIT) > to execute a function it defines. That works (or pretends to). However, if > I call the module's constructors first: > > > > exec_engine->runStaticConstructorsDestructors(false); > > exec_engine->runFunctionAsMain(function, argvec, NULL); > > > > execution still works, but my program crashes when it exits, in > __run_exit_handlers(). I can't tell from gdb what exit handler is crashing, > but no calls are made to atexit() or on_exit(); all exit handlers are > installed via __cxa_atexit(). > > &g...

...ExecutionEngine > (MCJIT) to execute a function it defines. That works (or pretends to). > However, if I call the module's constructors first: > > > > > > exec_engine->runStaticConstructorsDestructors(false); > > > exec_engine->runFunctionAsMain(function, argvec, NULL); > > > > > > execution still works, but my program crashes when it exits, in > __run_exit_handlers(). I can't tell from gdb what exit handler is crashing, > but no calls are made to atexit() or on_exit(); all exit handlers are > installed via __cxa_atexit(). &g...

...e > (MCJIT) to execute a function it defines. That works (or pretends to). > However, if I call the module's constructors first: > > > > > > > > exec_engine->runStaticConstructorsDestructors(false); > > > > exec_engine->runFunctionAsMain(function, argvec, NULL); > > > > > > > > execution still works, but my program crashes when it exits, in > __run_exit_handlers(). I can't tell from gdb what exit handler is crashing, > but no calls are made to atexit() or on_exit(); all exit handlers are > installed via __cxa_at...

Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler. Regards, Richard Gorton Cognitive Electronics rcgorton at cog-e.com ---------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: