search for: atmn

Hi James, On Fri, Sep 11, 2020 at 2:05 PM James Y Knight <jyknight at google.com> wrote: > > On Fri, Sep 11, 2020 at 12:42 PM Atmn Patel <atmndp at gmail.com> wrote: >> >> Hi Hal, >> >> On Thu, Sep 10, 2020 at 8:54 PM Hal Finkel <hfinkel at anl.gov> wrote: >> > >> > Hi, Atmn, >> > >> > Has anyone else expressed an opinion regarding the naming? We need to &...

Hi Hal, On Thu, Sep 10, 2020 at 8:54 PM Hal Finkel <hfinkel at anl.gov> wrote: > > Hi, Atmn, > > Has anyone else expressed an opinion regarding the naming? We need to > clarify the semantics in C, it seems. No other names have come in yet, in total the names proposed so far (I think) are: - maynotprogress - maybenoprogress - might_not_progress - nfpg - no_fpg and the loop metada...

Hi Nicolai and Hal, I was wondering if your present concerns regarding the directions of the proposed attributes and semantics of the current direction had been addressed, so I thought I'd send over a friendly ping. Have they? Atmn On Wed, Sep 9, 2020 at 1:08 AM Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > > > On 9/8/20 9:08 PM, Hal Finkel wrote: > > There is another thing that I would like for us to document: do > > infinite loops have any relationship to thread synchronization? As...

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, >...

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 >>...

...e correct code as per their language specs, and in addition, optimize out some dead loops that we weren’t able to optimize out before but could’ve. Feedback welcome. (The name of the function attribute and the loop metadata are still under discussion, and we’re definitely open to changing them.) Atmn and Johannes [1] https://bugs.llvm.org/show_bug.cgi?id=965 [2] https://lists.llvm.org/pipermail/llvm-dev/2015-July/088103.html [3] https://lists.llvm.org/pipermail/llvm-dev/2017-October/118558.html [4] https://reviews.llvm.org/D38336 [5] https://reviews.llvm.org/D65718 [6] https://eel.is/c++draft/...

On 9/7/20 10:56 AM, Nicolai Hähnle wrote: > Hi Johannes and Atmn, > > On Sat, Sep 5, 2020 at 7:07 AM Johannes Doerfert via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >>  > In any case, please explain the intended behavior of the attribute and >>  > the metadata upon inlining. >> >> The attribute will be at...

On 9/7/20 2:52 PM, Nicolai Hähnle wrote: > Hi Johannes, > > On Mon, Sep 7, 2020 at 6:51 PM Johannes Doerfert > <johannesdoerfert at gmail.com> wrote: >> On 9/7/20 10:56 AM, Nicolai Hähnle wrote: >>  > Hi Johannes and Atmn, >>  > >>  > On Sat, Sep 5, 2020 at 7:07 AM Johannes Doerfert via llvm-dev >>  > <llvm-dev at lists.llvm.org> wrote: >>  >>  > In any case, please explain the intended behavior of the >> attribute and >>  >>  > the metadata...