similar to: [LLVMdev] sqlite3 crashing jit

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-llvm > added. It should

I'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

At Thu, 15 Jul 2010 08:17:37 -0700, Peter Housel wrote: > The LLVM libraries provide the llvm::Intrinsic::getDeclaration() > function, which can provide a standard external declaration for any > of the (currently) 762 defined LLVM intrinsics, both for ordinary > intrinsics and for overrideable intrinsics with supplied parameter > types. Clients that do not link with the LLVM

The LLVM libraries provide the llvm::Intrinsic::getDeclaration() function, which can provide a standard external declaration for any of the (currently) 762 defined LLVM intrinsics, both for ordinary intrinsics and for overrideable intrinsics with supplied parameter types. Clients that do not link with the LLVM libraries (such as the Open Dylan compiler, which has its own IR and its own bitcode

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

Hi all, I install Ruby1.9.2po0 and Rails3.2.3 on RedHat5 When I create a project "rails nwe chapter" It show below error message: ************************************************************* Installing sqlite3 (1.3.5) with native extensions Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /usr/local/ruby/bin/ruby extconf.rb checking for

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

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 struct bar_struct bar; >    ... Definition

Is there any good reason for using DW_FORM_data1 for the DW_AT_language attribute of DW_TAG_compile_unit? This prevents using language codes in the DW_LANG_lo_user=0x8000 to DW_LANG_hi_user=0xffff range. I think the obvious change to use DW_FORM_data2 in line 1897 of lib/CodeGen/AsmPrinter/DwarfDebug.cpp should fix it. Or, if there are binary compatibility issues, the abbrev form could be chosen

On Tue Nov 04 2014 at 12:43:05 PM Peter S. Housel <housel at acm.org> wrote: > On 11/04/2014 07:04 AM, Robinson, Paul wrote: > >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Sean Silva > >> > >> You haven't established that you really need this. AFAIK Apple's linker > >> doesn't need this

On Wed, 2010-05-05 at 13:22 -0700, Nathan Jeffords wrote: > > The important point here is that the COFF MCSection needs to > have the right level of semantic information. In fact, > MCSection is the place that I'd start for COFF bringup. > > OK, I see that now. The current isolation > between TargetLoweringObjectFile ->

On May 6, 2010, at 11:22 PM, Nathan Jeffords wrote: > Thanks! Funny, I was just preparing a patch to submit for my changes to MCSectionCOFF. My changes look to be fairly independent of yours, my change was to deal with COMDAT's. I had dealt with the characteristics flags in the object writer, but I like this. If you don't mind I would like to merge my changes into this patch and submit

Thanks! Funny, I was just preparing a patch to submit for my changes to MCSectionCOFF. My changes look to be fairly independent of yours, my change was to deal with COMDAT's. I had dealt with the characteristics flags in the object writer, but I like this. If you don't mind I would like to merge my changes into this patch and submit it. I was just pondering how to deal with the

On Fri, May 7, 2010 at 12:05 AM, Chris Lattner <clattner at apple.com> wrote: > > On May 6, 2010, at 11:22 PM, Nathan Jeffords wrote: > > Thanks! Funny, I was just preparing a patch to submit for my changes to > MCSectionCOFF. My changes look to be fairly independent of yours, my change > was to deal with COMDAT's. I had dealt with the characteristics flags in the >

After chatting on IRC, Peter wants a very specific interrupt (int4 on x86). I suggested he add a new llvm.x86.int(i32) intrinsic, and use the existing branch on llvm.sadd.with.overflow intrinsic. The x86 backend can then turn jo+int4 into into when reasonable. -Chris On Aug 9, 2010, at 5:45 PM, Chris Lattner wrote: > > On Aug 9, 2010, at 10:44 AM, Peter S. Housel wrote: > >>

The enclosed patch contains a number of wording and clarity improvements to BitCodeFormat.html, and documents in detail the record types used within MODULE blocks. I plan to continue documenting the rest of the record types, but I wanted to submit patches in reasonably-sized pieces. -Peter S. Housel- housel at acm.org -------------- next part -------------- A non-text attachment was scrubbed...

Several instruction set architectures include arithmetic operations that can trap on overflow, or support this feature with a separate trap-on-overflow-flag instruction (such as the x86 INTO instruction). I am adding a back-end to the Open Dylan compiler to generate LLVM IR. The original back-end, which generates x86 machine code, makes use of the INTO instruction, and the runtime turns the

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,

With regard to Bartlett-style collectors, they are also used in CMUCL/SBCL, OpenDylan, and various products based on Ravenbrook's Memory Pool System. Also, while Mono doesn't use a Bartlett-style collector, it does support pinning objects referenced from ambiguous stack roots, in an otherwise copying collector. While ITA has expressed concerns with SBCL's GC, they seem to involve the