search for: charllsnotieneningunputocorreo

Hi, In llvm 3.0 llvm::ConstantArray had a ::getAsCString() method that returned the buffer as a std::string. Now it seems that 3.1 this method dissapeared. I found that llvm::ConstantDataArray has a method called getAsString(), but it returns a Constant*. What is the safe way to retrieve the pointer of the Constant array as a C string?

On 16 November 2012 13:55, charles quarra <charllsnotieneningunputocorreo at gmail.com> wrote: > In llvm 3.0 llvm::ConstantArray had a ::getAsCString() method that > returned the buffer as a std::string. Now it seems that 3.1 this > method dissapeared. > > I found that llvm::ConstantDataArray has a method called > getAsString(), but it returns a Cons...

i'm afraid this question is extremely basic, but i've assumed that dumping a .bc file from a module was a trivial operation, but now, first time i have to actually do it from code, for the life of me i can't find one missing step in the process: static void WriteModule ( const Module * M, BitstreamWriter & Stream )

...John t. -------- Original Message -------- Subject: Re: [LLVMdev] Fwd: updating module references in call instructions after a module clone Date: Thu, 06 Dec 2012 11:48:37 -0600 From: John Criswell <criswell at illinois.edu> Organization: University of Illinois To: charles quarra <charllsnotieneningunputocorreo at gmail.com> On 12/6/12 11:43 AM, charles quarra wrote: > (i hope bumping my own question as a way for begging attention is not > too frowned upon on the list, otherwise i can adjust the frequency as > low as required) > > > suppose module B has call/InvokeInst to calls in...

---------- Forwarded message ---------- From: charles quarra <charllsnotieneningunputocorreo at gmail.com> Date: 2012/12/13 Subject: error while linking modules with exception handling demo code To: llvmdev at cs.uiuc.edu Hi, I am building a module X with an arithmetic function foo, a module Y with an arithmetic function foo2 that invokes foo. For the invocation be a proper one (bei...

> De: Duncan Sands <baldrick at free.fr> >Para: >Enviado: miércoles, 11 de julio de 2012 9:40 >Asunto: Re: [LLVMdev] dynamic linkage for jit > >Hi Charllls, I didn't really get it. Are you saying that you would execute some >functions using the JIT then, later, those functions will be modified and thus >need to be re-jitted? > >Ciao, Duncan. Hi Duncan,

Hi, in ExceptionDemo code ( https://llvm.org/viewvc/llvm-project/llvm/trunk/examples/ExceptionDemo/ExceptionDemo.cpp?view=markup&sortby=file ) the function "ourPersonality" is defined. a llvm::Function is created with the same name inside function "createStandardUtilityFunctions". The llvm::Function is retrieved in function "createCatchWrappedInvokeFunction".

suppose module B has call/InvokeInst to calls in module A after i clone both modules i get B' and A' my concrete question is this: Are there any special steps that i need to do before linking the modules B' and A' together? my main concern is that B' will have call/InvokeInst pointing to module A, not A', and the linker will not be able to notice that it should replace

2013/3/27 Nick Lewycky <nicholas at mxc.ca>: > charles quarra wrote: >> >> Hi, >> >> I have two functions in a module, X.foo, which is the callee, and >> Y.foo2, which calls X.foo. >> >> If i either try to run llvm::Function::eraseFromParent() on any one of >> the functions, i'll >> get this assertion error: >> >> F is

2013/3/27 Nick Lewycky <nicholas at mxc.ca>: > charles quarra wrote: >> >> Hi, >> >> I have two functions in a module, X.foo, which is the callee, and >> Y.foo2, which calls X.foo. >> >> If i either try to run llvm::Function::eraseFromParent() on any one of >> the functions, i'll >> get this assertion error: >> >> F is

Hi, I have this module: ; ModuleID = './executableModule' @typeInfo0 = constant { i32 } zeroinitializer @typeInfo1 = constant { i32 } { i32 1 } @typeInfo2 = constant { i32 } { i32 2 } @typeInfo3 = constant { i32 } { i32 3 } @typeInfo4 = constant { i32 } { i32 4 } @typeInfo5 = constant { i32 } { i32 5 } @typeInfo6 = constant { i32 } { i32 6 } declare void @print32Int(i32, i8*) declare

Hi, I'm having an issue with the below modules. I build module X, then module Y (which has a dependency on X). I've added an external declaration on module Y of the functions defined in X. i also link the except-handling module, but i think it is peripheral to the issue i like all the modules together in a single module called executableModule. I link them with the method:

2013/3/27 Nick Lewycky <nicholas at mxc.ca>: >The common idiom to delete any Value* is: > > V->replaceAllUsesWith(UndefValue::get(V->getType()); > V->eraseFromParent(); > > Does that work for functions? You may need to make sure the 'undef' has a > pointer to function type instead of the function type. > I tried this code sample, passing the type

Hi, I have two functions in a module, X.foo, which is the callee, and Y.foo2, which calls X.foo. If i either try to run llvm::Function::eraseFromParent() on any one of the functions, i'll get this assertion error: F is used in instruction: %"calling function" = call i32 @X.foo(i32 %read) F is used in instruction: %"calling function" = call i32 @X.foo(i32 %read) While

2012/11/21 Kaylor, Andrew <andrew.kaylor at intel.com>: > If you re-JIT a module that you have previously linked to that will obviously cause some problems, but you can probably work around that with a stub function. could you elaborate a little bit on that ? i was thinking in something different; linking a cloned copy of the module rather than the module directly. Would that work

Hi, JIT does not allow functions to call others in different modules, so all modules need to be statically linked in a big fat module. If a module needs to be recompiled, all the others need to as well as relinked. there are two ways i intend to approach this problem: 1) forget about JITing, build each module into a .bc, call gcc to generate .soname libraries, dynamically load with dlopen()