Displaying 3 results from an estimated 3 matches for "mayprogress".
2020 Sep 10
2
[RFC] Introducing the maynotprogress IR attribute
...I would agree that we should write this down though.
>
>
> > I suspect that we may need specific handling (if nothing
> > else, so we don't sink stores past possibly-infinite loops).
>
> If (possibly-)infinite loops are well defined, e.g., in a function with
> the `mayprogress` attribute, we certainly cannot move any effect past
> them. If they are not, they are UB if they loop infinitely and otherwise
> finite and therefore a no-op. So we can either delete them, by assuming
> they are finite, or, if we know they are not, actually eliminate
> anything that is...
2020 Sep 09
2
[RFC] Introducing the maynotprogress IR attribute
On 9/5/20 12:40 AM, Atmn Patel wrote:
> On Sat, Sep 5, 2020 at 1:07 AM Johannes Doerfert
> <johannesdoerfert at gmail.com> wrote:
>>
>> 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
2020 Sep 11
4
[RFC] Introducing the maynotprogress IR attribute
...t;
> >>
> >> > I suspect that we may need specific handling (if nothing
> >> > else, so we don't sink stores past possibly-infinite loops).
> >>
> >> If (possibly-)infinite loops are well defined, e.g., in a function with
> >> the `mayprogress` attribute, we certainly cannot move any effect past
> >> them. If they are not, they are UB if they loop infinitely and otherwise
> >> finite and therefore a no-op. So we can either delete them, by assuming
> >> they are finite, or, if we know they are not, actually elim...