search for: llvmgetnexttarget

...hile (Target <> nil) do >> begin >> // get target name & description >> TargetName := LLVMGetTargetName(Target); >> TargetDescription := LLVMGetTargetDescription(Target); >> >> // do something with these information >> >> Target := LLVMGetNextTarget(Target); >> end; >> > I don't see any obvious problems here, though someone else might. > What exactly is the problem you are seeing? Is LLVMGetFirstTarget > returning NULL? LLVMGetFirstTarget returns a pointer at a quite high address. Subsequent calls to LLVMGetNextTarge...

...rget 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; By debugging the LLVM library (a custom DLL, which works fine otherwise), I can see that there is no information, but I'm not that deep into C and the LLVM structure to identify what went wrong. Also I did a lot of tests the other day, trying several things without luck. However...

...ntil 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; > I don't see any obvious problems here, though someone else might. What exactly is the problem you are seeing? Is LLVMGetFirstTarget returning NULL? You may want to take a look at this code: http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/radeon/radeon_...

...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

...e > 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 &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: > > >

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