Displaying 7 results from an estimated 7 matches for "gomp_loop_runtime_next".
2010 Dec 22
2
[LLVMdev] Generating target dependent function calls
Hi,
raghesh and I are working in Polly on automatically generating OpenMP
calls. This works nicely on a 64bit architecture,
however the functions we need to generate are slightly different on
different platforms.
The reason for the difference is that e.g "long" in
> bool GOMP_loop_runtime_next(long, long)
has a different size on different architectures.
Currently we generate the prototypes and functions ourselves:
> declare i8 @GOMP_loop_runtime_next(i64*, i64*) nounwind
To support a 32bit architecture we would need to generate:
> declare i8 @GOMP_loop_runtime_next(i32*, i32*)...
2010 Dec 26
2
[LLVMdev] Generating target dependent function calls
...ally generating OpenMP
>> calls. This works nicely on a 64bit architecture,
>> however the functions we need to generate are slightly different on
>> different platforms.
>>
>> The reason for the difference is that e.g "long" in
>>
>> > bool GOMP_loop_runtime_next(long, long)
>>
>> has a different size on different architectures.
>>
>> Currently we generate the prototypes and functions ourselves:
>> > declare i8 @GOMP_loop_runtime_next(i64*, i64*) nounwind
>>
>> To support a 32bit architecture we would need to...
2010 Dec 22
0
[LLVMdev] Generating target dependent function calls
...king in Polly on automatically generating OpenMP
> calls. This works nicely on a 64bit architecture,
> however the functions we need to generate are slightly different on
> different platforms.
>
> The reason for the difference is that e.g "long" in
>
> > bool GOMP_loop_runtime_next(long, long)
>
> has a different size on different architectures.
>
> Currently we generate the prototypes and functions ourselves:
> > declare i8 @GOMP_loop_runtime_next(i64*, i64*) nounwind
>
> To support a 32bit architecture we would need to generate:
> > declar...
2010 Dec 26
0
[LLVMdev] Generating target dependent function calls
>>>
>>>
>>> The reason for the difference is that e.g "long" in
>>>
>>>> bool GOMP_loop_runtime_next(long, long)
>>>
>>> has a different size on different architectures.
>>>
>>> Currently we generate the prototypes and functions ourselves:
>>>> declare i8 @GOMP_loop_runtime_next(i64*, i64*) nounwind
>>>
>>> To support a 32bit arc...
2010 Dec 26
1
[LLVMdev] Generating target dependent function calls
On 12/26/2010 01:31 AM, Eric Christopher wrote:
>>>>
>>>>
>>>> The reason for the difference is that e.g "long" in
>>>>
>>>>> bool GOMP_loop_runtime_next(long, long)
>>>>
>>>> has a different size on different architectures.
>>>>
>>>> Currently we generate the prototypes and functions ourselves:
>>>>> declare i8 @GOMP_loop_runtime_next(i64*, i64*) nounwind
>>>>
>>>&g...
2011 Sep 12
0
[LLVMdev] multi-threading in llvm
Hi Alexandra,
I don't know much, maybe this topic should be bridged with polly-dev
(adding it to CC) to bring it more attention.
Indeed, polly uses ScopPass, that creates serious limitations in
compatibility with other passes. To my understanding, scops are used
because ISL loop analysis tool uses scops. In fact, just for handling
OpenMP directives scops are not required, unless one need to
2011 Sep 08
4
[LLVMdev] multi-threading in llvm
Hi,
I want to execute the iterations of a loop in parallel, by inserting calls either to pthreads or to the gomp library at the LLVM IR level. As a first step, I inserted an omp pragma in a C file and compiled it with llvm-gcc to check the generated LLVM code. If I understand correctly, to parallelize the loop in LLVM IR, I have to separate the loop in a new function, put all required parameters