Displaying 6 results from an estimated 6 matches for "pthread_barrier_wait".
2009 Oct 08
0
[LLVMdev] Instructions that cannot be duplicated
...blem.
> After looking at the llvm IR, there is no equivalent method of
> representing an instruction that is an execution barrier(not a memory
> barrier, which llvm.barrier.[ss|ll|ls|sl] is). If you have any idea's,
> we would be willing to give them a try.
Is the effect similar to pthread_barrier_wait(barrier_for($pc))
[http://linux.die.net/man/3/pthread_barrier_wait] where the
implementation automatically generates the barrier_for() function and
automatically calculates the number of threads to wait for?
If the barrier lowers to any sort of function call, it sounds like
you're currently l...
2009 Oct 08
2
[LLVMdev] Instructions that cannot be duplicated
...e llvm IR, there is no equivalent method of
> > representing an instruction that is an execution barrier(not a memory
> > barrier, which llvm.barrier.[ss|ll|ls|sl] is). If you have any
> idea's,
> > we would be willing to give them a try.
>
> Is the effect similar to pthread_barrier_wait(barrier_for($pc))
> [http://linux.die.net/man/3/pthread_barrier_wait] where the
> implementation automatically generates the barrier_for() function and
> automatically calculates the number of threads to wait for?
>
> If the barrier lowers to any sort of function call, it sounds li...
2009 Oct 08
2
[LLVMdev] Instructions that cannot be duplicated
> -----Original Message-----
> From: Eli Friedman [mailto:eli.friedman at gmail.com]
> Sent: Wednesday, October 07, 2009 5:50 PM
> To: Villmow, Micah
> Cc: LLVM Developers Mailing List
> Subject: Re: [LLVMdev] Instructions that cannot be duplicated
>
> On Wed, Oct 7, 2009 at 11:20 AM, Villmow, Micah
<Micah.Villmow at amd.com>
> wrote:
> > Is there a current
2009 Oct 08
0
[LLVMdev] Instructions that cannot be duplicated
...equivalent method of
>> > representing an instruction that is an execution barrier(not a memory
>> > barrier, which llvm.barrier.[ss|ll|ls|sl] is). If you have any
>> idea's,
>> > we would be willing to give them a try.
>>
>> Is the effect similar to pthread_barrier_wait(barrier_for($pc))
>> [http://linux.die.net/man/3/pthread_barrier_wait] where the
>> implementation automatically generates the barrier_for() function and
>> automatically calculates the number of threads to wait for?
>>
>> If the barrier lowers to any sort of function...
2009 Oct 08
3
[LLVMdev] Instructions that cannot be duplicated
...;>> > representing an instruction that is an execution barrier(not a memory
>>> > barrier, which llvm.barrier.[ss|ll|ls|sl] is). If you have any
>>> idea's,
>>> > we would be willing to give them a try.
>>>
>>> Is the effect similar to pthread_barrier_wait(barrier_for($pc))
>>> [http://linux.die.net/man/3/pthread_barrier_wait] where the
>>> implementation automatically generates the barrier_for() function and
>>> automatically calculates the number of threads to wait for?
>>>
>>> If the barrier lowers to...
2012 Feb 15
2
[PATCH 0/2] Make appliance building thread-safe (RHBZ#790721).
These two patches make appliance building thread-safe. The first adds
a test which easily demonstrates the problem. The second fixes the
issue.
For more information see Ian McLeod's analysis of the bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=790528#c5
Rich.