Displaying 4 results from an estimated 4 matches for "_assuming".
Did you mean:
assuming
2020 Sep 07
2
[RFC] Introducing the maynotprogress IR attribute
...t scheduler schedules execution of multiple threads.
>> >> > That is, it is talking about the dynamic behavior of the
>> >> > implementation. On the other hand, the proposed attribute presumably
>> >> > makes a statement about the program itself _assuming that_ its
>> >> > execution gets scheduled. So there is no applicable definition of
>> >> > "progress" in the cited section of the C++ spec.
>> >>
>> >> I don't understand. What is the alternative to "assuming that i...
2020 Sep 07
2
[RFC] Introducing the maynotprogress IR attribute
...uot;progress" it is referring to
> how some abstract scheduler schedules execution of multiple threads.
> That is, it is talking about the dynamic behavior of the
> implementation. On the other hand, the proposed attribute presumably
> makes a statement about the program itself _assuming that_ its
> execution gets scheduled. So there is no applicable definition of
> "progress" in the cited section of the C++ spec.
I don't understand. What is the alternative to "assuming that its
execution gets scheduled"?
~ Johannes
> Cheers,
> Nicolai
&...
2020 Sep 07
4
[RFC] Introducing the maynotprogress IR attribute
...gt;> > how some abstract scheduler schedules execution of multiple threads.
>> > That is, it is talking about the dynamic behavior of the
>> > implementation. On the other hand, the proposed attribute presumably
>> > makes a statement about the program itself _assuming that_ its
>> > execution gets scheduled. So there is no applicable definition of
>> > "progress" in the cited section of the C++ spec.
>>
>> I don't understand. What is the alternative to "assuming that its
>> execution gets scheduled&qu...
2020 Sep 05
4
[RFC] Introducing the maynotprogress IR attribute
On 9/4/20 7:39 PM, Hal Finkel via llvm-dev wrote:
>
> On 9/4/20 6:31 PM, Atmn Patel via llvm-dev wrote:
>> Hi All,
>>
>> We’ve prepared a new function attribute `maynotprogress` and loop
>> metadata `llvm.loop.mustprogress` in order to better formalize the way
>> LLVM deals with infinite loops without observable side-effects. This
>> is deeply