search for: llvmgetfirsttarget

...list-module-globals ditto * --disassemble Test llvm-c/Disassebler.h. Not sure about input format, lines of cpu name + hexdumped asm maybe is easiest for FileCheck * --objdump Test llvm-c/Object.h. List sections and symbols of an object file. * --list-targets LLVMGetFirstTarget/LLVMGetNextTarget and whatever can be extracted from them * --calc Test Core.h irbuilding and possibly executionengine. Create a module with a function evaluating the specified aritmetic expression. Possibly generating machinecode and executing. anders

...gt; * --disassemble > Test llvm-c/Disassebler.h. Not sure about input format, > lines of cpu name + hexdumped asm maybe is easiest for FileCheck > > * --objdump > Test llvm-c/Object.h. List sections and symbols of an object file. > > * --list-targets > LLVMGetFirstTarget/LLVMGetNextTarget and whatever can be extracted > from them > > * --calc > Test Core.h irbuilding and possibly executionengine. Create a module > with a function evaluating the specified aritmetic expression. > Possibly generating machinecode and executing. &g...

I like the idea, but I find the name confusing; I think it should have `llvm-c` or `c-api` somewhere in the name. This could also serve as a simple example of using the API. -- Sean Silva On Mon, Sep 23, 2013 at 4:00 PM, Anders Waldenborg <anders at 0x63.nu> wrote: > Moving this to llvmdev. > > On Fri, Sep 20, 2013 at 08:26:41AM +0200, Anders Waldenborg wrote: > > >

...here? >> >> // initialize all targets / target information >> LLVMInitializeAllTargets; >> LLVMInitializeAllTargetInfos; >> >> // initialize native target in particular >> LLVMInitializeNativeTarget; >> >> // get first target >> Target := LLVMGetFirstTarget; >> >> // loop until the target is NULL >> while (Target <> nil) do >> begin >> // get target name & description >> TargetName := LLVMGetTargetName(Target); >> TargetDescription := LLVMGetTargetDescription(Target); >> >> // do...

Moving this to llvmdev. On Fri, Sep 20, 2013 at 08:26:41AM +0200, Anders Waldenborg wrote: > > > This avoids warnings when included in a application that > > > uses -Wstrict-prototypes. > > > > > > > Should we enable this warning in CFLAGS for LLVM builds to catch this > > sooner? > > It is a C-only warning, and AFAICS there is no C code in

...lowing code is written in Pascal, can you please tell me if I have done something wrong here? // initialize all targets / target information LLVMInitializeAllTargets; LLVMInitializeAllTargetInfos; // initialize native target in particular LLVMInitializeNativeTarget; // get first target Target := LLVMGetFirstTarget; // loop until the target is NULL while (Target <> nil) do begin // get target name & description TargetName := LLVMGetTargetName(Target); TargetDescription := LLVMGetTargetDescription(Target); // do something with these information Target := LLVMGetNextTarget(Target); end;...

...ell me if I have done something wrong here? > > // initialize all targets / target information > LLVMInitializeAllTargets; > LLVMInitializeAllTargetInfos; > > // initialize native target in particular > LLVMInitializeNativeTarget; > > // get first target > Target := LLVMGetFirstTarget; > > // loop until the target is NULL > while (Target <> nil) do > begin > // get target name & description > TargetName := LLVMGetTargetName(Target); > TargetDescription := LLVMGetTargetDescription(Target); > > // do something with these information &...

Attached is what I got thus far. What I'm struggling with is proper integration in build system. What is in there is just wild guesses from my side, both on autoconf and cmake variants. It would be great if someone with proper knowledge of the buildsystems could have a look. Also I'm not sure how to properly handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is

...LVMCreateTargetMachine to work on my box (MBP i7 OS X 10.8). What should the values of triple, cpu and features be? I'm just looking for a way to get this up and going for now, I don't need specific optimizations. No matter what I send the function, I always get nil back. I'm giving it LLVMGetFirstTarget as the target value. Thanks for the help, Timothy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121226/13cf56e2/attachment.html>