search for: housel

...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 conditionally. Are there? Thanks -Peter S. Housel- housel at acm.org

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

...rge in small independent patches as they are built. Please review Peter's patch (since you know COFF :). I'll take a look tomorrow and apply it if you think it is forward progress, and if there aren't other issues. Thanks! -Chris > > On Thu, May 6, 2010 at 11:12 PM, Peter S. Housel <housel at acm.org> wrote: > 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...

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

...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 PrintSwitchToSection function without needing the IsDirective flag. On Thu, May 6, 2010 at 11:12 PM, Peter S. Housel <housel at acm.org> wrote: > 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...

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

...they are built. Please > review Peter's patch (since you know COFF :). I'll take a look tomorrow and > apply it if you think it is forward progress, and if there aren't other > issues. > > Thanks! > > -Chris > > > On Thu, May 6, 2010 at 11:12 PM, Peter S. Housel <housel at acm.org> wrote: > >> 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, >> &...

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... Name: BitCodeFormat.diff Type: text/x-patch Size: 27026 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091026/d50d9bcc/attachment.bin>

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

...86). 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: > >> 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 co...

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 create executable `test.llvm' which is a just...

...Peter's patch (since you know COFF :). I'll take a look tomorrow and >> apply it if you think it is forward progress, and if there aren't other >> issues. >> >> Thanks! >> >> -Chris >> >> >> On Thu, May 6, 2010 at 11:12 PM, Peter S. Housel <housel at acm.org> wrote: >> >>> 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 informati...

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

On Aug 9, 2010, at 10:44 AM, Peter S. Housel wrote: > 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 LL...

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>

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

On Tue, 27 Apr 2010 10:22:49 -0600, Charles Davis <cdavis at mymail.mines.edu> wrote: > Not yet. We're working on it, though: > > http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html Is anyone actively working on adding ELF object file support to the MC project?

> Is anyone actively working on adding ELF object file support to the MC > project? I'm not aware of anyone. Same for COFF. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

The enclosed patch adds documentation for the PARAMATTR_BLOCK, TYPE_BLOCK, and TYPE_SYMTAB_BLOCK records in the LLVM IR bitcode format. I have started documenting CONSTANTS_BLOCK and FUNCTION_BLOCK and will send patches when they are complete. -Peter- -------------- next part -------------- An HTML attachment was scrubbed... URL:

...lvm 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-llvm > added. It should create executable `test.llvm' which is a just...