similar to: [LLVMdev] dynamic typing system

The dump from the function I'm running: define %object_structure @0() { entry: ret %object_structure { i8 0, %object_union [double 5.000000e+00, double false] } } the only output I get after the runFunction() call is: UNREACHABLE executed! Stack dump: 0. Running pass 'X86 DAG->DAG Instruction Selection' on function '@0' I just noticed that my union seems to look like

Tthe IRBuilder APIs for unions or unions in general? Either way, I was using unions as a temporary solution for a problem I was too lazy to fully figure out anyway. On Sun, Aug 15, 2010 at 4:54 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Alec Benzer wrote: > >> The dump from the function I'm running: >> >> define %object_structure @0() { >> entry:

Alec Benzer wrote: > The dump from the function I'm running: > > define %object_structure @0() { > entry: > ret %object_structure { i8 0, %object_union [double 5.000000e+00, > double false] } > } Unions are almost entirely unimplemented. Sorry. > the only output I get after the runFunction() call is: > > UNREACHABLE executed! > Stack dump: > 0. Running

What does this error mean? I'm getting it from an ExecutionEngine::runFunction() call. The function I'm passing it was run through verifyFunction() right before the runFunction() call. I can't seem to find anything that tells me what causes this, only specific (but seemingly unrelated to my problem) cases of it happening. -------------- next part -------------- An HTML attachment was

Hi, In my llvm code I want to create some function calls. The function prototype is as follows: int memoize ( char *function_name, int *int_params, unsigned num_ints, double *double_params, unsigned num_doubles) In order to create these calls I do the following for example: %88 = alloca [7 x i8] store volatile [7 x i8] c"ORACLE\00", [7 x i8]*

The blog post I linked to implied that adding a symbol in the form lle_X_FUNCTIONNAME would allow you to call a function called FUNCTIONNAME. Is this not the case? On Thu, Aug 19, 2010 at 6:46 PM, <o.j.sivart at gmail.com> wrote: > You are adding the symbol as "lle_X_create_number_object" yet your error > message implies you have tried to lookup and use

Alec Benzer <alecbenzer at gmail.com> writes: > Ok, so calling lle_X_FUNCTIONNAME instead of FUNCTIONNAME works (is there > any reason the post used the lle_X_ prefix other than convention? was it > once possible to call external functions as I was originally trying, or, why > did the blog post think it was possible?) AFAIK you can name the function as you please (with some

Stack colouring should be able to reuse the same stack space, if the live ranges of the pointers don't overlap. But I don't think anyone has built a general solution for alloca'd space. On Mon, Nov 4, 2013 at 6:30 AM, Ali Javadi <aj14889 at yahoo.com> wrote: > Hi, > > In my llvm code I want to create some function calls. The function > prototype is as follows: >

On Aug 15, 2010, at 1:06 PM, Alec Benzer wrote: > What does this error mean? I'm getting it from an ExecutionEngine::runFunction() call. The function I'm passing it was run through verifyFunction() right before the runFunction() call. I can't seem to find anything that tells me what causes this, only specific (but seemingly unrelated to my problem) cases of it happening. Which

> I'm afraid that you might be utterly confused about how to use LLVM. Er, I don't think so? I think I was mostly just confused about interfacing with external functions, since whoever wrote that blog post ( http://www.gearleaf.com/blog/post/44) didn't seem to know what he was talking about (or he was doing stuff that once worked but now doesn't? I don't know). If you

Is there documentation somewhere on how to call external functions from llvm? The only guide I found was this: http://www.gearleaf.com/blog/post/44, and it doesn't seem to be working for me. I have a function: llvm::GenericValue lle_X_create_number_object(llvm::FunctionType* ft, const std::vector<llvm::GenericValue>& args) { llvm_object_structure* result = new

Ok, so calling lle_X_FUNCTIONNAME instead of FUNCTIONNAME works (is there any reason the post used the lle_X_ prefix other than convention? was it once possible to call external functions as I was originally trying, or, why did the blog post think it was possible?) I'm now running into trouble when trying to access arguments however. printing args.size() from the function yields

Yeah, sounds good to me. I strongly support ripping them out of mainline completely. -Chris On Aug 15, 2010, at 2:39 PM, Anton Korobeynikov wrote: > Hi, Chris > > What do you think about this? > > > ---------- Forwarded message ---------- > From: Nick Lewycky <nicholas at mxc.ca> > Date: Mon, Aug 16, 2010 at 01:34 > Subject: Re: [LLVMdev] "UNREACHABLE

You are adding the symbol as "lle_X_create_number_object" yet your error message implies you have tried to lookup and use "create_number_object". Can you provide the code for the lookup? On 20/08/2010, at 8:07 AM, Alec Benzer wrote: > Is there documentation somewhere on how to call external functions from llvm? The only guide I found was this:

On 12 January 2011 23:38, Rob Nikander <rob.nikander at gmail.com> wrote: > I have to pass something from the LinkageTypes enum to the > constructor.  I tried others, like GlobalVariable::InternalLinkage, > which dumps as "internal global" but the error was the same. To be honest, your IR is a bit odd. I'm not a JIT expert, but here are a few things that will help you

On Wed, Jan 12, 2011 at 6:08 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 12 January 2011 22:28, Rob Nikander <rob.nikander at gmail.com> wrote: >> @x = external global %0* > > Hi Rob, > > Try removing the 'extern', as it implies the variable storage is > elsewhere (ie. another object file). > I have to pass something from the

On Wed, Sep 25, 2013 at 5:50 PM, Filip Pizlo <fpizlo at apple.com> wrote: > Hi all, > > TBAA on loads and stores is super useful for conveying high-level type > knowledge to LLVM transformations. But often translating a high-level > language into LLVM IR will result in runtime calls that are known at the > high level to only affect (either by reading or by writing) some

On Oct 7, 2013, at 3:49 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > > On Wed, Sep 25, 2013 at 5:50 PM, Filip Pizlo <fpizlo at apple.com> wrote: > Hi all, > > TBAA on loads and stores is super useful for conveying high-level type knowledge to LLVM transformations. But often translating a high-level language into LLVM IR will result in runtime calls

Howdy do LLVM folks! I've exhausted what I can do on my own to make a GC example bind (usual googling, reading, playing, looking at source). I can't find the shadow collector lib or perhaps the -l options needed to link my sample (not even to point where I'm figuring out GC actually as I can't link). Not sure this IR is correct but here is what I've been playing

Hello, Sorry for my stupid mistakes. I hope that everything is fine now. This patch fixes PR2218. There are no loads in example, however "instcombine" changes memcpy() into store/load. Regards, Jakub Staszak -------------- next part -------------- A non-text attachment was scrubbed... Name: pr2218-2.patch Type: application/octet-stream Size: 6525 bytes Desc: not available URL: