search for: omp_fork_call

Displaying 14 results from an estimated 14 matches for "omp_fork_call".

2017 Jan 21
2
[RFC] IR-level Region Annotations
...ntrinsic_a? > > — > Mehdi > > > >> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. >> 2. perform outlining. >> >> Caller code >> .... >> omp_push_num_threads(4) >> omp_fork_call( .... outline_par_region....) .... >> >> Callee code: >> Outlined_par_rgion { >> I32* priv_val = alloca 32 >> I32* priv_i = .... >> >> Ret >> } >> >> For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it ru...
2017 Jan 20
5
[RFC] IR-level Region Annotations
...gnostic supposed to behave in face of llvm.experimental.intrinsic_a? — Mehdi > 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. > 2. perform outlining. > > Caller code > .... > omp_push_num_threads(4) > omp_fork_call( .... outline_par_region....) .... > > Callee code: > Outlined_par_rgion { > I32* priv_val = alloca 32 > I32* priv_i = .... > > Ret > } > > For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it runs correctly w/ and w/o optimizations...
2017 Feb 01
0
[RFC] IR-level Region Annotations
...ntrinsic_a? > > — > Mehdi > > > >> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. >> 2. perform outlining. >> >> Caller code >> .... >> omp_push_num_threads(4) >> omp_fork_call( .... outline_par_region....) .... >> >> Callee code: >> Outlined_par_rgion { >> I32* priv_val = alloca 32 >> I32* priv_i = .... >> >> Ret >> } >> >> For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it ru...
2017 Feb 01
2
[RFC] IR-level Region Annotations
...> >> >> >>> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. >>> 2. perform outlining. >>> >>> Caller code >>> .... >>> omp_push_num_threads(4) >>> omp_fork_call( .... outline_par_region....) .... >>> >>> Callee code: >>> Outlined_par_rgion { >>> I32* priv_val = alloca 32 >>> I32* priv_i = .... >>> >>> Ret >>> } >>> >>> For OpenMP, we do support it at -O0, -O1, -O...
2017 Feb 01
0
[RFC] IR-level Region Annotations
...> >> >> >>> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. >>> 2. perform outlining. >>> >>> Caller code >>> .... >>> omp_push_num_threads(4) >>> omp_fork_call( .... outline_par_region....) .... >>> >>> Callee code: >>> Outlined_par_rgion { >>> I32* priv_val = alloca 32 >>> I32* priv_i = .... >>> >>> Ret >>> } >>> >>> For OpenMP, we do support it at -O0, -O1, -O...
2017 Jan 20
9
[RFC] IR-level Region Annotations
Hi Sanjoy, Yes, that's exactly what we have been looking at recently here, but the region tags seem to make it possible to express the control flow as well, so I think we could start with reg ions+metadata, as Hal and Xinmin proposed, and then figure out what needs to be first class instructions. --Vikram Adve > On Jan 19, 2017, at 11:03 PM, Sanjoy Das <sanjoy at
2017 Feb 01
1
[RFC] IR-level Region Annotations
...t;>>> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. >>>> 2. perform outlining. >>>> >>>> Caller code >>>> .... >>>> omp_push_num_threads(4) >>>> omp_fork_call( .... outline_par_region....) .... >>>> >>>> Callee code: >>>> Outlined_par_rgion { >>>> I32* priv_val = alloca 32 >>>> I32* priv_i = .... >>>> >>>> Ret >>>> } >>>> >>>> For O...
2017 Jan 20
3
[RFC] IR-level Region Annotations
...c_a? > > — > Mehdi > > > > >> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and >> replace all %val with %prv_val in the region. >> 2. perform outlining. >> >> Caller code >> .... >> omp_push_num_threads(4) >> omp_fork_call( .... outline_par_region....) .... >> >> Callee code: >> Outlined_par_rgion { >> I32* priv_val = alloca 32 >> I32* priv_i = .... >> >> Ret >> } >> >> For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make >> su...
2017 Feb 01
0
[RFC] IR-level Region Annotations
...i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. >>>>> 2. perform outlining. >>>>> >>>>> Caller code >>>>> .... >>>>> omp_push_num_threads(4) >>>>> omp_fork_call( .... outline_par_region....) .... >>>>> >>>>> Callee code: >>>>> Outlined_par_rgion { >>>>> I32* priv_val = alloca 32 >>>>> I32* priv_i = .... >>>>> >>>>> Ret >>>>> } >>...
2017 Feb 01
2
[RFC] IR-level Region Annotations
...it, the question is how it an openmp agnostic supposed to behave in face of llvm.experimental.intrinsic_a? — Mehdi 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. 2. perform outlining. Caller code .... omp_push_num_threads(4) omp_fork_call( .... outline_par_region....) .... Callee code: Outlined_par_rgion { I32* priv_val = alloca 32 I32* priv_i = .... Ret } For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it runs correctly w/ and w/o optimizations and advanced analysis. So we need to preserve all source...
2017 Feb 01
1
[RFC] IR-level Region Annotations
..._a? > > — > Mehdi > > > > >> 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and >> replace all %val with %prv_val in the region. >> 2. perform outlining. >> >> Caller code >> .... >> omp_push_num_threads(4) >> omp_fork_call( .... outline_par_region....) .... >> >> Callee code: >> Outlined_par_rgion { >> I32* priv_val = alloca 32 >> I32* priv_i = .... >> >> Ret >> } >> >> For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to >> make s...
2017 Feb 01
0
[RFC] IR-level Region Annotations
...e of llvm.experimental.intrinsic_a? > > — > Mehdi > > > > 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. > 2. perform outlining. > > Caller code > .... > omp_push_num_threads(4) > omp_fork_call( .... outline_par_region....) .... > > Callee code: > Outlined_par_rgion { > I32* priv_val = alloca 32 > I32* priv_i = .... > > Ret > } > > For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it runs correctly w/ and w/o optimizations and...
2017 Feb 01
2
[RFC] IR-level Region Annotations
...it, the question is how it an openmp agnostic supposed to behave in face of llvm.experimental.intrinsic_a? — Mehdi 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. 2. perform outlining. Caller code .... omp_push_num_threads(4) omp_fork_call( .... outline_par_region....) .... Callee code: Outlined_par_rgion { I32* priv_val = alloca 32 I32* priv_i = .... Ret } For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it runs correctly w/ and w/o optimizations and advanced analysis. So we need to preserve all source...
2017 Feb 01
2
[RFC] IR-level Region Annotations
...e of llvm.experimental.intrinsic_a? > > — > Mehdi > > > > 1. create i32* priv_val = alloca i32 %priv_i = ...in the region, and replace all %val with %prv_val in the region. > 2. perform outlining. > > Caller code > .... > omp_push_num_threads(4) > omp_fork_call( .... outline_par_region....) .... > > Callee code: > Outlined_par_rgion { > I32* priv_val = alloca 32 > I32* priv_i = .... > > Ret > } > > For OpenMP, we do support it at -O0, -O1, -O2 and -O3. We had to make sure it runs correctly w/ and w/o optimizations and...