Displaying 16 results from an estimated 16 matches for "oscarfv".
Did you mean:
oscar
2006 Apr 14
2
[LLVMdev] Re: standalone llvm
On Fri, 14 Apr 2006 03:25:39 +0200
Oscar Fuentes <oscarfv at telefonica.net> wrote:
...
> Simon,
>
> With a fresh CVS checkout, I've tried your test case on Windows/VC++
> and it works ok. Too bad that I have not access to a Linux machine
> right now. I'll like to see what's wrong with your test case.
>
> What you ge...
2006 Apr 14
2
[LLVMdev] Re: standalone llvm
On Thu, 13 Apr 2006 18:07:42 +0200
Oscar Fuentes <oscarfv at telefonica.net> wrote:
>
> Simon Burton <simon at arrowtheory.com> writes:
>
> > I'm trying to take assembly and create machine code I can execute.
> > How close am I ?
>
> Your test case is not complete. Besides, which version of llvm are you
> usi...
2006 Apr 15
2
[LLVMdev] Re: how to code a loop in llvm assembly
Simon Burton <simon at arrowtheory.com> writes:
> Hi,
>
> I've read over the "LLVM Language Reference Manual"
> a few times, and writing some ll code, but i'm stuck at
> a very basic point. How to decrement a counter variable ?
>
> int %count(int %n) {
> EntryBlock:
> %cond = seteq int %n, 0
> br bool %cond, label %Exit, label %Next
>
2006 Apr 15
6
[LLVMdev] how to code a loop in llvm assembly
Hi,
I've read over the "LLVM Language Reference Manual"
a few times, and writing some ll code, but i'm stuck at
a very basic point. How to decrement a counter variable ?
int %count(int %n) {
EntryBlock:
%cond = seteq int %n, 0
br bool %cond, label %Exit, label %Next
Next:
; how to decrement n ?
%new_n = sub int %n, 1
br label %EntryBlock
Exit:
ret int 0
}
I guess I
2006 Apr 13
0
[LLVMdev] Re: standalone llvm
Simon Burton <simon at arrowtheory.com> writes:
> I'm trying to take assembly and create machine code I can execute.
> How close am I ?
Your test case is not complete. Besides, which version of llvm are you
using? What are the commands for compiling and linking your test case?
How it bombs?
Do you #include "llvm/ExecutionEngine/JIT.h" ?
--
Oscar
2006 Apr 14
0
[LLVMdev] Re: standalone llvm
Simon Burton <simon at arrowtheory.com> writes:
> I'm using llvm CVS, and manage to compile/link OK. Yes I include JIT.h.
> The program segfaults when it gets to calling the function pointer.
>
>>From the Makefile:
>
> llvmjit: llvmjit.o
> g++ llvmjit.o /home//users//simonb//lib/LLVMAsmParser.o /home//users//simonb//lib/LLVMInterpreter.o `llvm-config --ldflags`
2006 Apr 14
0
[LLVMdev] Re: standalone llvm
Simon Burton <simon at arrowtheory.com> writes:
>> There are several possibilities here: either add1 is assigned a NULL
>> pointer, or LLVM was unable to use the JIT and generates bytecode
>> instead of native code, or invalid native code was generated
>> (unlikely).
>
> Well, it's not NULL:
>
> (gdb) print add1
> $1 = (int (*)(int)) 0x83e43b8
>
2006 Apr 14
1
[LLVMdev] Re: standalone llvm
On Fri, 14 Apr 2006 04:05:10 +0200
Oscar Fuentes <oscarfv at telefonica.net> wrote:
>
> This indicates that the JIT is not working and your code is being
> interpreted. I don't know about "llvm-config --libs jit" you are using
> but I would try adding LLVMJIT.o to your link command the same way you
> do with LLVMInterpret...
2006 Apr 17
0
[LLVMdev] Re: how to code a loop in llvm assembly
On Sat, 15 Apr 2006 07:47:00 +0200
Oscar Fuentes <oscarfv at telefonica.net> wrote:
>
> BTW, Simon, is there a reason for writing LLVM assembler and not
> generating LLVM code directly?
You mean write C++ code that calls the LLVM library ?
I have a mild C++ allergy that I don't wish to aggravate.
> The later is simpler and relieves...
2006 Apr 13
2
[LLVMdev] standalone llvm
On Wed, 12 Apr 2006 23:02:12 -0500 (CDT)
Chris Lattner <sabre at nondot.org> wrote:
>
> > I'd like to directly create executable code that i can
> > stick in memory somewhere and jump into (call).
>
> Take a look at the llvm/examples directory. There are several small
> programs that create LLVM IR on the fly and JIT compile it.
I'm trying to take
2011 Jan 05
0
[LLVMdev] include/Config/config.h discrepancies between CMake and autofoo builds
Eric Christopher <echristo at apple.com> writes:
>>> Or cleanup both headers from unused stuff by Eric's
>>> suggestion?
>>
>> I'm not sure this is a good idea (not that it is bad either). Murphy's
>> Law says that a function that you remove today will be used tomorrow.
>
> I meant literally functions that aren't used in the
2006 Apr 22
0
[LLVMdev] Re: Building CFE on MinGW
Greg Pettyjohn <gregp at ccs.neu.edu> writes:
> I've blown a couple of weekends trying to build under MinGW.
>
> I can build the llvm tools with only a couple of minor hassles, but can't
> seem to make any headway with the C Front End
>
> Most errors I run into involve not being able to find header files.
> The most frustrating part is that the error messages
2006 Apr 22
0
[LLVMdev] Re: Building CFE on MinGW
Greg Pettyjohn <gregp at ccs.neu.edu> writes:
> Is the MinGW user's list on the web?
Look on www.mingw.org -> mailing list
> Can you give me a link to the thread?
Sorry, no time for that. Once on the mailing list archives, do a
search for 'configure'.
> (What's IIRC?)
If I Remember Correctly.
By the way, what's your configure command?
--
Oscar
2006 Apr 23
0
[LLVMdev] Re: Building CFE in Mingw
Anton Korobeynikov <asl at math.spbu.ru> writes:
[snip]
> 2) Problem: Complains about gthr-default.h file.
> Resolution: Grab gcc/gcc/gthr-win32.h file and copy it to gthr-default.h
... so --enable-threads=win32 is broken... good to know.
> 3) Problem: Complains about "CL_ObjCXX" and simular ("CL_") during
> compilation
2008 Feb 09
1
[LLVMdev] Annotate a value.
Hello.
It would be very useful for my project being able to annotate
Value's. An int would do fine.
I found an old message with this same subject talking about the
Annotation interface and Annotable object, but the doxygen graphs says
that only Function is annotable.
Could I use the ValueName for the job? It would be enough, although
quite clumsy. Seems that Value's of type void
2006 Apr 23
0
[LLVMdev] Re: Building CFE on MinGW
Greg Pettyjohn <gregp at ccs.neu.edu> writes:
> I'm using a little shell script:
[snip]
> confopts="--prefix=$PREFIX"
> confopts="$confopts --disable-threads"
> confopts="$confopts --disable-nls"
> confopts="$confopts --disable-shared"
> confopts="$confopts --enable-languages=c,c++"
>