similar to: [LLVMdev] LLVM-C Patch : LLVMConvertModuleToC

On Sep 16, 2010, at 5:35 AM, F van der Meeren wrote: > LLVMConvertModuleToC Patch to LLVM-C > > <LLVMConvertModuleToCPatch> > *shrug* One of the things about the C API is that it's a "support forever" sort of thing. Is this kind of thing a big enough use case that we want to have an API specifically for it? -eric

I don't see why not. C is a worthy language, one that I think we should fully support. And by just providing some minor features really limits its usefulness. Right now, at this very instance it isn't usable. Except as a stepping stone to the bigger framework. But thats just my 2 cents. - Filip On 16 Sep 2010, at 19:51, Eric Christopher wrote: > > On Sep 16, 2010, at 5:35 AM, F

On Sep 16, 2010, at 11:00 AM, F van der Meeren wrote: > I don't see why not. > C is a worthy language, one that I think we should fully support. > And by just providing some minor features really limits its usefulness. > Right now, at this very instance it isn't usable. Except as a stepping stone to the bigger framework. > > But thats just my 2 cents. Been thinking

I could extract all the functionality into wrapper methods. So that it would be possible to create such a thing in C. But without considering the coding standards (it comes directly out of my repository), why would you object against this? It seemed logical to me, to be able to create code in C, and then generate C out of it. This would be useful in things like a new flex/bison. And combining

> > >> And combining modules is something that seemed a primitive to me. > > Why not just wrap the Linker interface? To be more specific, why not just wrap certain specific Linker calls instead of another big function that does a huge amount of work? -eric

On 17 Sep 2010, at 23:14, Eric Christopher wrote: >> >> >>> And combining modules is something that seemed a primitive to me. >> >> Why not just wrap the Linker interface? > > To be more specific, why not just wrap certain specific Linker calls instead of another big function that does a huge amount of work? > > -eric Done, and I will make an

I am going to post my first chapter, just to see if it is acceptable. Any feedback is good feedback for me. Filip On 31 Aug 2010, at 17:25, Rajika Kumarasiri wrote: > Most of the documents (html) are generated using rst2html. So I think a patch to the rst file in llvm/tools/llvmc/doc should be fine. > > Rajika > > On Mon, Aug 30, 2010 at 7:59 PM, F van der Meeren

I think it'd be nice to have a ToC describing what you plan to cover in the "hello world" tutorial. I'll take a look at the tutorial in the week end and send feed back. Rajika On Wed, Sep 1, 2010 at 2:02 AM, F van der Meeren <llvm-dev at code2develop.com>wrote: > I am going to post my first chapter, just to see if it is acceptable. > Any feedback is good feedback

I am still having some trouble finding my way in the C++ files. Could you give me a clearer direction? Filip On 13 Sep 2010, at 18:39, Charles Davis wrote: > On 9/13/10 10:32 AM, F van der Meeren wrote: >> Hello, >> >> I am trying to emit C code from the module I just created. And this from LLVM-C. >> If someone could give me a pointer on how to do this in llvm (with

On Sep 13, 2010, at 10:40 AM, F van der Meeren wrote: > I am still having some trouble finding my way in the C++ files. > Could you give me a clearer direction? If you have llvm IR then you can use 'llc' to generate c code. Try $ llc <input_llvm_ir> -march=c -o /tmp/output.c This C backend is implemented in llvm/lib/Target/CBackend - Devang

On Sep 16, 2010, at 11:58 AM, F van der Meeren wrote: > I could extract all the functionality into wrapper methods. So that it would be possible to create such a thing in C. > But without considering the coding standards (it comes directly out of my repository), why would you object against this? Because nothing else works that way and I don't see expanding the C API to include various

As I have stated before, I am creating a LLVM-C tutorial. Now I expect it to be in a final draft form within 2~3 weeks, but how do I have to deliver it to the community? - File format ? - Style ? - ... Thank you, Filip

What do you guys/girls think about LLVM-C additions that are similar to the following: char * LLVMConvertModuleToC(LLVMModuleRef aModule); Which creates the X-code for a given module (in this case for the language C). - Filip -------------- next part -------------- An HTML attachment was scrubbed... URL:

Most of the documents (html) are generated using rst2html. So I think a patch to the rst file in llvm/tools/llvmc/doc should be fine. Rajika On Mon, Aug 30, 2010 at 7:59 PM, F van der Meeren <llvm-dev at code2develop.com > wrote: > As I have stated before, I am creating a LLVM-C tutorial. > Now I expect it to be in a final draft form within 2~3 weeks, but how do I > have to

Hi, Is it possible to create a .dll / .so / .dylib by only using the LLVM-C headers ? If so, I cannot find it. Filip

Hi, I am trying to get started with the llvm-c headers. Is there any place where I can get/retrieve documentation about it? Such as a basic tutorial, memory managment... Thank you, Filip

That was all I needed to hear :-) Because I am already at "chapter 3", which is regular expressions in C, but then made so that each regex becomes a real and true function. And doubt suddenly struck. What if my style isn't exactly what the LLVM community wants... On 01 Sep 2010, at 15:09, nessim wrote: > hey Filip, > > I'm afraid i can't give you technical

Hello, I have a question concerning llvm-c. I have set up a function that needs to invoke an external method, in a other library. It has the following signature: void* NSFullUserName(void); The void* can be replaced with a i8*, that far I was able to get, but when my call is invoked, the engine gives me the following message: LLVM ERROR: Tried to execute an unknown external function: i8* ()*

That won't work when you are trying to limit yourself to C and only C. Is there an LLVM-C alternative? Filip On 07 Sep 2010, at 20:37, Eric Christopher wrote: > > On Sep 7, 2010, at 11:30 AM, F van der Meeren wrote: > >> >> >> Any ideas on what I am doing wrong here ? >> > > > Why not just use something like: > > const Type

Hello, I have a question, what is wrong with the following code? declare void @llvm.memcpy.p0i64.p0i64.i8(i64*, i64*, i8, i32, i1) nounwind ... call void @llvm.memcpy.p0i64.p0i64.i8(i64* %19, i64* %21, i8 %17, i32 0, i1 false) ... According to the compiler this is the error, but I seem to miss where exactly my fault is. Intrinsic prototype has incorrect number of arguments! void (i64*,