search for: cilk

Displaying 20 results from an estimated 43 matches for "cilk".

2017 Jan 19
2
[RFC] IR-level Region Annotations
...y minimal changes > >> to analysis and especially transformation passes. > > > > TAPIR is an elegant, small extension and, in particular, I think the > idea of asymmetric parallel tasks and control flow is a clever way to > express parallelism with serial semantics, as in Cilk. Encoding the > control flow extensions as explicit instructions is orthogonal to that, > though arguably more elegant than using region tags + metadata. > > > > However, Cilk is a tiny language compared with the full complexity of > other languages, like OpenMP. To take just...
2017 Jan 19
3
[RFC] IR-level Region Annotations
...t;> >> to analysis and especially transformation passes. >> > >> > TAPIR is an elegant, small extension and, in particular, I think the >> idea of asymmetric parallel tasks and control flow is a clever way to >> express parallelism with serial semantics, as in Cilk. Encoding the >> control flow extensions as explicit instructions is orthogonal to that, >> though arguably more elegant than using region tags + metadata. >> > >> > However, Cilk is a tiny language compared with the full complexity of >> other languages, like O...
2012 Oct 02
7
[LLVMdev] [RFC] Parallelization metadata and intrinsics in LLVM (for OpenMP, etc.)
...) and semantics. LLVM is a language-neutral IR and infrastructure and OpenMP-specific concepts should not creep into it. I've included an excerpt from Hal's proposal below, which shows what I mean: the design is couched in terms of OpenMP parallel regions. Other parallel languages, e.g, Cilk, have no such notion. The latest Intel proposal is at least as OpenMP-specific. I do agree with the general goal of trying to support parallel programming languages in a more first-class manner in LLVM than we do today. But the right approach for that is to be as language-neutral as possible. F...
2012 Oct 02
0
[LLVMdev] [RFC] Parallelization metadata and intrinsics in LLVM (for OpenMP, etc.)
...o be to push some of the OpenMP-specific nature of the loop into the IR. This is not necessarily bad. > I've included an excerpt from > Hal's proposal below, which shows what I mean: the design is couched > in terms of OpenMP parallel regions. Other parallel languages, e.g, > Cilk, have no such notion. The approach that I proposed was certainly inspired by OpenMP, and designed to fully support OpenMP, but was not limited to it. As a practical matter, OpenMP includes both loop-based parallelism and task-based parallelism, which is a pretty broad foundation for supporting par...
2017 Jan 20
2
[RFC] IR-level Region Annotations
...;>> > >>> > TAPIR is an elegant, small extension and, in particular, I >>> think the idea of asymmetric parallel tasks and control flow >>> is a clever way to express parallelism with serial >>> semantics, as in Cilk. Encoding the control flow extensions >>> as explicit instructions is orthogonal to that, though >>> arguably more elegant than using region tags + metadata. >>> > >>> > However, Cilk is a tiny language compared with the ful...
2012 Oct 02
1
[LLVMdev] [RFC] Parallelization metadata and intrinsics in LLVM (for OpenMP, etc.)
...MP-specific nature of the loop into > the IR. This is not necessarily bad. > > > I've included an excerpt from > > Hal's proposal below, which shows what I mean: the design is couched > > in terms of OpenMP parallel regions. Other parallel languages, e.g, > > Cilk, have no such notion. > > The approach that I proposed was certainly inspired by OpenMP, and > designed to fully support OpenMP, but was not limited to it. As a > practical matter, OpenMP includes both loop-based parallelism and > task-based parallelism, which is a pretty broad found...
2017 Jan 20
9
[RFC] IR-level Region Annotations
...lly transformation passes. >>>>> >>>>> TAPIR is an elegant, small extension and, in particular, I think the >>>>> idea of asymmetric parallel tasks and control flow is a clever way to >>>>> express parallelism with serial semantics, as in Cilk. Encoding the control >>>>> flow extensions as explicit instructions is orthogonal to that, though >>>>> arguably more elegant than using region tags + metadata. >>>>> >>>>> However, Cilk is a tiny language compared with the full complex...
2017 Jan 19
4
[RFC] IR-level Region Annotations
...ts and it seemed to work well with only minimal changes > to analysis and especially transformation passes. TAPIR is an elegant, small extension and, in particular, I think the idea of asymmetric parallel tasks and control flow is a clever way to express parallelism with serial semantics, as in Cilk. Encoding the control flow extensions as explicit instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. However, Cilk is a tiny language compared with the full complexity of other languages, like OpenMP. To take just one example, TAPIR cannot express...
2013 Mar 03
0
[LLVMdev] parallel loop metadata simplification
...hope mem2reg/SROA makes the loop parallel, but unfortunately it serializes some of the valid parallel loop cases too. Improved version would generate loop-scope (temporary) variables in a parallel-loop aware way. BTW I noted Clik Plus has actually two different parallel loop constructs. Have you, Cilk Plus developers, thought about the parallel loop code generation yet? BR, -- --Pekka
2017 Jan 21
2
[RFC] IR-level Region Annotations
...;>> TAPIR is an elegant, small extension and, in particular, I think >>>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>>> instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. >>>>>>>> >>>>>>>> However, Cilk is a tiny language compared with...
2015 Feb 16
3
[LLVMdev] LLVM parallel annotations
...4D4702B0C3E38B35.4D4702B0C3E38B35&CFID=627318069&CFTOKEN=29416610&__acm__=1424122362_bed7c2b9ae0d0280ccf90b472978b74a>] lately, so I will be starting off from there in order to design a good parallel representation. With this patch a lot of the modern parallel C interfaces (pthreads, cilk, openMP etc.) will be translated to one unified LLVM IR. My goal is to make this part of the LLVM mainstream branch eventually. I'd really like to discuss design considerations that you might have, or any objections or pointers (pun intended). It is also possible somebody is already working on...
2017 Jan 20
5
[RFC] IR-level Region Annotations
...;>>>>> TAPIR is an elegant, small extension and, in particular, I think >>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>> instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. >>>>>>> >>>>>>> However, Cilk is a tiny language compared with the full &g...
2017 Jan 20
3
[RFC] IR-level Region Annotations
...>>> TAPIR is an elegant, small extension and, in particular, I think >>>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>>> instructions is orthogonal to that, though arguably more elegant >>>>>>>> than using region tags + metadata. >>>>>>>> >>>>>>>> However, Cilk is...
2018 Jun 07
2
[RFC] Abstract Parallel IR Optimizations
...s of the used parallel representation. While this sounds tedious at first, it turns out that we can perform key optimizations with reasonable implementation effort (and thereby also reasonable maintenance costs). However, we have various parallel representations that are already in use (KMPC, GOMP, CILK runtime, ...) or proposed (Tapir, IntelPIR, ...). Our proposal seeks to introduce parallelism specific optimizations for multiple representations while minimizing the implementation overhead. This is done through an abstract notion of a parallel region which hides the actual representation from t...
2017 Feb 01
0
[RFC] IR-level Region Annotations
...;>> TAPIR is an elegant, small extension and, in particular, I think >>>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>>> instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. >>>>>>>> >>>>>>>> However, Cilk is a tiny language compared with...
2017 Feb 01
2
[RFC] IR-level Region Annotations
...PIR is an elegant, small extension and, in particular, I think >>>>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>>>> instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. >>>>>>>>> >>>>>>>>> However, Cilk is a tiny language co...
2017 Feb 01
1
[RFC] IR-level Region Annotations
...trinsic, and it is probably better to call a spade a spade and represent it as a new instruction. [XT] Yes and No. Yes: w.r.t region scope annotation, No: it is more than one new instruction, it is more like a sequence of instructions. Assume we have a "fork" instruction, omp fork and cilk fork/spawn semantics are differently in terms of stack frame allocation and ABI. When we introduce a new instruction, the exact semantics needs to be defined, it can't be alter. Thus, we proposed to start with experimental_intrinsics, and it is proven working. We can always convert the intrin...
2017 Feb 01
0
[RFC] IR-level Region Annotations
...PIR is an elegant, small extension and, in particular, I think >>>>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>>>> instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. >>>>>>>>> >>>>>>>>> However, Cilk is a tiny language co...
2013 Apr 14
0
[LLVMdev] C++AMP -> OpenCL (NVPTX) prototype
...don't know much about AMP, but I do have users who are also interested in accelerator targeting, and I'd like you to share your thoughts on: 1. Does your implementation share common functionality with the 'captured statement' work that Intel is currently doing (in order to support Cilk, OpenMP, etc.)? If you're not aware of it, see: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20130408/077615.html -- This should end up in trunk soon. I ask because if the current captured statement patches would almost, but not quite, work for you, then it would be interesting to...
2017 Feb 01
1
[RFC] IR-level Region Annotations
...egant, small extension and, in particular, I think >>>>>>>>>> the idea of asymmetric parallel tasks and control flow is a >>>>>>>>>> clever way to express parallelism with serial semantics, as in >>>>>>>>>> Cilk. Encoding the control flow extensions as explicit >>>>>>>>>> instructions is orthogonal to that, though arguably more elegant than using region tags + metadata. >>>>>>>>>> >>>>>>>>>> However, Cilk is a tiny...