search for: openmp31_stat

...tness. A large constraint on the design of a metadata API is that OK, I see. I suppose it's not a big deal to add the scheduling property. At least if one (later) allows adding scheduling modes supported by other standards than OpenMP as well. I.e., not modes like "static" but "openmp31_static" or similar. For OpenCL work item loops the scheduling mode could be "auto" or left empty. > I agree. I think that vectorization is best done earlier in the > optimization schedule. Vectorization, however, should appropriately > update loop metadata to allow for proper in...

On Mon, 13 Aug 2012 12:38:02 +0300 Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi> wrote: > Hi, > > On 08/10/2012 11:06 PM, Hal Finkel wrote: > > I'd like to see support in clang/LLVM for multi-core parallelism, > > especially support for OpenMP. I think that the best way to do > > this is by designing an LLVM-based API (metadata and intrinsics) >

...metadata API is > > that > > OK, I see. > > I suppose it's not a big deal to add the scheduling property. At > least if one (later) allows adding scheduling modes supported by other > standards than OpenMP as well. I.e., not modes like "static" but > "openmp31_static" or similar. For OpenCL work item loops the > scheduling mode could be "auto" or left empty. I think that this makes sense. For some things, like 'static', we can define backend-independent semantics. For other things, like OpenMP's 'runtime', which is tied...