search for: denbuen

On Tue, 10 Aug 2010 13:42:05 -0600 "Bueno, Denis" <denbuen at sandia.gov> wrote: > Hello, > http://www.opendylan.org/~housel/bcdump.pl > I'm trying to compile sqlite3 using llvm-gcc, then run it with lli. sqlite3 is part of LLVM testsuite, so it shouldn't crash ... > This builds with the exact same flags as above, but with -emit-l...

On Fri, Apr 9, 2010 at 2:11 PM, Bueno, Denis <denbuen at sandia.gov> wrote: > Hello all, > > I'm trying to understand a bit of LLVM IR syntax.  I have a function > definition which looks like this in IR: > >    define void @foo(%1* ptr) { ... > > The C code for foo has a definition that looks like: > >    typedef s...

Hello, I'm trying to compile sqlite3 using llvm-gcc, then run it with lli. I've attached a Makefile and a main.c that simply invokes sqlite3_initialize(). You'll need to download sqlite3 (it was too big to attach) and copy main.c and the Makefile into the directory where sqlite3.c is [Link: sqlite-amalgamation-3_7_0_1.zip <http://www.sqlite.org/sqlite-amalgamation-3_7_0_1.zip>

Hello all, I'm trying to understand a bit of LLVM IR syntax. I have a function definition which looks like this in IR: define void @foo(%1* ptr) { ... The C code for foo has a definition that looks like: typedef struct bar_struct bar; ... Definition of struct bar_struct ... void foo(bar *ptr) { ... I can't whittle down a convenient test source file just now; but

...9;m trying to get a stacktrace, so I can't provide one. I'm trying llvm 2.7 right now. I'm hoping there's a 2.6 workaround, though. On 8/10/10 2:01 PM, "Török Edwin" <edwintorok at gmail.com> wrote: On Tue, 10 Aug 2010 13:42:05 -0600 "Bueno, Denis" <denbuen at sandia.gov> wrote: > Hello, > http://www.opendylan.org/~housel/bcdump.pl > I'm trying to compile sqlite3 using llvm-gcc, then run it with lli. sqlite3 is part of LLVM testsuite, so it shouldn't crash ... > This builds with the exact same flags as above, but with -emit-l...

On Aug 10, 2010, at 5:09 PM, Reid Kleckner wrote: No, he's just on linux x86_64 using JITed frames with no unwind information. That was the whole point of adding the support here: http://llvm.org/docs/DebuggingJITedCode.html See if you can get a stack trace using the directions there. I had followed the directions on that page with llvm 2.6 to no avail. The Makefile I posted does use

On Fri, Apr 9, 2010 at 3:11 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Fri, Apr 9, 2010 at 2:11 PM, Bueno, Denis <denbuen at sandia.gov> wrote: >> Hello all, >> >> I'm trying to understand a bit of LLVM IR syntax.  I have a function >> definition which looks like this in IR: >> >>    define void @foo(%1* ptr) { ... >> >> The C code for foo has a definition that lo...

On Tue, Aug 10, 2010 at 1:35 PM, Eric Christopher <echristo at apple.com> wrote: > > On Aug 10, 2010, at 1:30 PM, Bueno, Denis wrote: > >> Running lli under gdb gives >> >> Program received signal SIGSEGV, Segmentation fault. >> [address] in ?? () >> (gdb) bt >> #0 [address] in ?? () >> Cannot access memory at address [address2] >>

On 8/10/10 2:39 PM, "Dale Johannesen" <dalej at apple.com> wrote: > What environment is this? Some JITs work better than others. Ubuntu Lucid, x86_64. -Denis

On Aug 10, 2010, at 2:01 PM, Török Edwin wrote: > Did you try llvm-2.7? Just tried LLVM 2.7. Exactly the same. No backtrace as before. I must be doing something stupid. Can anyone reproduce this using my Makefile? -Denis

Actually, there is one difference. This time I got a warning in gdb about "JITed object file architecture i386 is not compatible with the target architecture i386:x86_64". In my Makefile, I passed -m32 to llvm-gcc because that's what I want. Taking that out causes it to work in LLVM 2.7. -Denis On Aug 10, 2010, at 3:38 PM, Bueno, Denis wrote: > > On Aug 10, 2010, at 2:01

On Aug 10, 2010, at 3:46 PM, Eric Christopher wrote: > You may be trying to JIT something for x86-32 on x86-64? Try setting up the jit for x86-32. How do I do that? Is it a runtime flag for lli? Or do I need to configure llvm differently? -Denis

Hello, I'm trying to compile some existing C99 code with llvm in order to take advantage of its whole-program optimisations. The existing code has a configure/make compilation process. So far the most success I've had follows this recipe: CC=llvmc ./configure make CFLAGS='--emit-llvm ...' #including a bunch of gcc optimisation flags like -O2 The compile process first builds

Running lli under gdb gives Program received signal SIGSEGV, Segmentation fault. [address] in ?? () (gdb) bt #0 [address] in ?? () Cannot access memory at address [address2] Was sqlite3 part of the llvm-2.6 test suite? If so, it is likely there's a workaround for 2.6. On 8/10/10 2:25 PM, "Eric Christopher" <echristo at apple.com> wrote: On Aug 10, 2010, at 1:09 PM,