search for: cilk_for

...and am looking for some feedback on my approach. The motivation for trying to use copy captures is to avoid unnecessary loads that are otherwise required inside the outlined function. This can be important when the outlined function represents the body of a loop, and cannot be inlined, such as in cilk_for, or using a library-based parallel for with lambdas. I have been prototyping an LLVM IR pass that can move loads out of a captured statement body when possible. The approach: Use named metadata to find the captured statement helpers (or lambda functions), as well as the "kind" of captu...

On 03/02/2013 08:44 PM, Tobias Grosser wrote: > If the use of ivdep is correct, it seems necessary to _not_ annotate the loads > and stores from and to 't'. Only after 't' is moved into a register, the loop is > actually parallel on the IR level. I didn't realize this is a problem in general because in pocl we explicitly "privatize" the OpenCL C kernel

On 03/01/2013 10:05 PM, Redmond, Paul wrote: [...] > I have discovered that you can provide a custom inserter to IRBuilder (who knew!). This has basically solved all my problems and allowed me to generate the proper metadata with minimal changes to clang codegen. Currently it adds the metadata to all loads and stores but I don't think this is a problem and can be refined later if necessary.

On Sat, Nov 2, 2013 at 2:48 PM, Rob Stewart <robstewart57 at gmail.com> wrote: > Hi, I'm getting started with LLVM, with the intention of writing a DSL > that compiles to LLVM IR, to target a new CPU instruction set. I have > two questions: > > 1. Multimedia IO in LLVM > > In the paper "The LLVM Instruction Set and Compilation Strategy" [1], > there is

Hi, I'm getting started with LLVM, with the intention of writing a DSL that compiles to LLVM IR, to target a new CPU instruction set. I have two questions: 1. Multimedia IO in LLVM In the paper "The LLVM Instruction Set and Compilation Strategy" [1], there is talk about a possible multimedia instruction set in a future LLVM release: "Note that LLVM is a virtual instruction

> (d) Add a small number of LLVM intrinsics for region or loop annotations, > represent the directive/clause names using metadata and the remaining > information using arguments. > > Here we're proposing (d), I think this would serve the goal of communicating source-level directives and annotations down to LLVM passes and back-ends, while deferring inlining and

A Proposal for adding an experimental IR-level region-annotation infrastructure ============================================================================= Hal Finkel (ANL) and Xinmin Tian (Intel) This is a proposal for adding an experimental infrastructure to support annotating regions in LLVM IR, making use of intrinsics and metadata, and a generic analysis to allow transformations to