Displaying 3 results from an estimated 3 matches for "global_sign".
Did you mean:
globalsign
2020 Sep 10
2
[RFC] Introducing the maynotprogress IR attribute
...I doubt we guarantee that now, though we might not actively exploit it.
> I also think we should not treat termination as synchronization, at
> least not in the case where progress is required. So, in C (and arguably
> we might want to do this also in C++), we would say that:
> ```
> global_signal = 1;
> while (1);
> ```
> is well defined and we will not remove the write.
>
> FWIW, 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-infini...
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 not actively exploit it.
> >> I also think we should not treat termination as synchronization, at
> >> least not in the case where progress is required. So, in C (and arguably
> >> we might want to do this also in C++), we would say that:
> >> ```
> >> global_signal = 1;
> >> while (1);
> >> ```
> >> is well defined and we will not remove the write.
> >>
> >> FWIW, I would agree that we should write this down though.
> >>
> >>
> >> > I suspect that we may need specific handling (if...