search for: latencyzero

On Jan 10, 2013, at 22:10 , Sean Silva <silvas at purdue.edu> wrote: > On Thu, Jan 10, 2013 at 8:25 AM, Rick Mann <rmann at latencyzero.com> wrote: >> I've been writing up my experience embedding LLVM in a Cocoa app. If anyone would like to see it and give feedback, I'd appreciate it. It's still not finished, but the first part is there: >> >> http://roderickmann.org/stuff/LLVMTut/HowToEmbed...

...nt Computational Scientist > Leadership Computing Facility > Argonne National Laboratory > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -- Rick Mann rmann at latencyzero.com

On 27 Oct 2015, at 09:48, Senthil Kumar <senthil.thecoder at gmail.com> wrote: > > Haven't worked on this yet, but I work on the gcc AVR backend (and binutils), and I'm very interested in this - I intend to work on it in my spare time. And do you have any comments / objections to Dylan becoming the code owner? David

I've been writing up my experience embedding LLVM in a Cocoa app. If anyone would like to see it and give feedback, I'd appreciate it. It's still not finished, but the first part is there: http://roderickmann.org/stuff/LLVMTut/HowToEmbedLLVMWithXcode.html If it's worthy, hopefully it'll end up in the LLVM docs. -- Rick

On Jan 8, 2013, at 13:55 , "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote: > You need to include 'llvm/ExecutionEngine/JIT.h' (or 'llvm/ExecutionEngine/JIT.h' if you want that engine) from your main file. Including that file forces the JIT static constructor to be linked into your executable. Without it, the JIT static constructor gets optimized out and

On Thu, Jan 10, 2013 at 8:25 AM, Rick Mann <rmann at latencyzero.com> wrote: > I've been writing up my experience embedding LLVM in a Cocoa app. If anyone would like to see it and give feedback, I'd appreciate it. It's still not finished, but the first part is there: > > http://roderickmann.org/stuff/LLVMTut/HowToEmbedLLVMWithXcod...

I've been working through the getting started and language reference docs. One thing that's not immediately clear if it's possible is to define a global pointer to a specific memory address. I'm looking at ways to use LLVM to target a small ARM embedded processor, and there are a great many hardware registers mapped into the address space. I tried making a little sample C program

On Apr 9, 2010, at 23:32:12, Chris Lattner wrote: > Several people have asked what the MC project is all about, and it is now getting to a point where it is pretty interesting and there are lots of potential projects for people who are interested. I wrote a big post about what it is here: > http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html Thanks for the post, Chris. It

Rick Mann <rmann at latencyzero.com> writes: > On Jan 8, 2013, at 13:55 , "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote: > >> You need to include 'llvm/ExecutionEngine/JIT.h' (or >> llvm/ExecutionEngine/JIT.h' if you want that engine) from your main >> file. Including...

On Thu, Jan 10, 2013 at 8:25 AM, Rick Mann <rmann at latencyzero.com> wrote: > I've been writing up my experience embedding LLVM in a Cocoa app. If > anyone would like to see it and give feedback, I'd appreciate it. It's > still not finished, but the first part is there: > > http://roderickmann.org/stuff/LLVMTut/HowToEmbedL...

On Thu, Jan 10, 2013 at 5:28 PM, Rick Mann <rmann at latencyzero.com> wrote: > > On Jan 10, 2013, at 14:21 , Justin Holewinski <justin.holewinski at gmail.com> > wrote: > > > That's a very nice start! Do you plan on sandboxing the execution? It > seems like just blindly executing the compiled code could easily crash the >...

Hi. I've had moderate success so far with LLVM. I've got an OS X app in Xcode that is able to parse my DSL, generate code into an LLVM Module, and pass it to an ExecutionEngine to execute. But now I'm stuck. That code needs to reference an external function I define in my app. If I define that function in the same source file as the file that invokes the ExecutionEngine, everything

On Dec 12, 2013, at 04:25 , Gasiunas, Vaidas <vaidas.gasiunas at sap.com> wrote: > To address these requirements we have developed a set of patches improving performance and malfunction safety of certain compiler passes and would be interested in contributing them at some point. Before proposing concrete changes, we would like to know what the general interest is with respect to making

Hi list, Does LLVM provide support for Apple-style blocks? Or is that all implemented in clang using LLVM primitives? I'm looking at the IR that clang generates, and it sure seems confusing to me. I'm hoping there's a builder that can help me implement them. Thanks! -- Rick

You'll want to look at clang/lib/CodeGen/CGBlocks.[cpp, h]. -eric On Thu, Jan 17, 2013 at 7:26 PM, Rick Mann <rmann at latencyzero.com> wrote: > Hi list, > > Does LLVM provide support for Apple-style blocks? Or is that all > implemented in clang using LLVM primitives? I'm looking at the IR that > clang generates, and it sure seems confusing to me. I'm hoping there's a > builder that can help m...

On Jan 17, 2013, at 19:33 , Eric Christopher <echristo at gmail.com> wrote: > You'll want to look at clang/lib/CodeGen/CGBlocks.[cpp, h]. Thanks. I think proper blocks are way over my head for my little project. I'll try to implement something "block-like" using function pointers. -- Rick

On Jan 23, 2013, at 21:47 , Sean Silva <silvas at purdue.edu> wrote: > Try running the verifier pass (the one that is invoked by `opt -verify`). I'm not sure how to do this. I'm writing a Cocoa app that calls the LLVM API directly; I don't use any of the command-line tools. Is there a way to verify via API? I think I've actually done this for individual types, dunno

It is a pass that can be run like any other pass. See createVerifierPass(). -- Sean Silva On Thu, Jan 24, 2013 at 12:50 AM, Rick Mann <rmann at latencyzero.com> wrote: > > On Jan 23, 2013, at 21:47 , Sean Silva <silvas at purdue.edu> wrote: > >> Try running the verifier pass (the one that is invoked by `opt -verify`). > > I'm not sure how to do this. I'm writing a Cocoa app that calls the LLVM API directly; I don&...

Several people have asked what the MC project is all about, and it is now getting to a point where it is pretty interesting and there are lots of potential projects for people who are interested. I wrote a big post about what it is here: http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html Thoughts and comments welcome, -Chris

On Feb 13, 2013, at 17:26 , Lang Hames <lhames at gmail.com> wrote: > LLVMContext was designed to support multithreading by holding the compilation context for each thread in a separate LLVMContext. If you're building modules in parallel you definitely need one LLVMContext per thread. > > If you're talking about compiling multiple modules sequentially with a single context