Displaying 4 results from an estimated 4 matches for "openmp11".
2012 Oct 02
0
[LLVMdev] [RFC] OpenMP Representation in LLVM IR
.../ language constructs at all.
>
> Also, we’d like to keep opportunities for optimization of parallel
> code as widely opened as possible –obviously, within the boundaries of
> preserving correct semantics of a user program.
>
> And finally, in the spirit of OpenMP Specification ([OpenMP11]), LLVM
> IR based compilers should be able to easily skip IR extensions related
> to OpenMP support and still generate correct, albeit sequential, code.
>
>
> Function Outlining
> ==================
> Eventually, parallel regions should be put into separate routines, a
> pr...
2012 Sep 28
11
[LLVMdev] [RFC] OpenMP Representation in LLVM IR
...without
adding any new types / language constructs at all.
Also, we’d like to keep opportunities for optimization of parallel
code as widely opened as possible –obviously, within the boundaries of
preserving correct semantics of a user program.
And finally, in the spirit of OpenMP Specification ([OpenMP11]), LLVM
IR based compilers should be able to easily skip IR extensions related
to OpenMP support and still generate correct, albeit sequential, code.
Function Outlining
==================
Eventually, parallel regions should be put into separate routines, a
process usually called “function outlini...
2012 Oct 03
0
[LLVMdev] [RFC] OpenMP Representation in LLVM IR
...language constructs at all.
>
> Also, we’d like to keep opportunities for optimization of parallel
> code as widely opened as possible –obviously, within the boundaries of
> preserving correct semantics of a user program.
>
> And finally, in the spirit of OpenMP Specification ([OpenMP11]), LLVM
> IR based compilers should be able to easily skip IR extensions related
> to OpenMP support and still generate correct, albeit sequential, code.
>
>
> Function Outlining
> ==================
> Eventually, parallel regions should be put into separate routines, a
>...
2012 Sep 28
0
[LLVMdev] [RFC] OpenMP Representation in LLVM IR
...language constructs at all.
>
> Also, we’d like to keep opportunities for optimization of parallel
> code as widely opened as possible –obviously, within the boundaries of
> preserving correct semantics of a user program.
>
> And finally, in the spirit of OpenMP Specification ([OpenMP11]), LLVM
> IR based compilers should be able to easily skip IR extensions related
> to OpenMP support and still generate correct, albeit sequential, code.
>
>
> Function Outlining
> ==================
> Eventually, parallel regions should be put into separate routines, a
>...