search for: laurenzo

Per the recent (seeming) consensus regarding incubating new projects under the LLVM organization, I would like to trial the process by requesting to incubate mlir-npcomp <https://github.com/google/mlir-npcomp>. The project is still quite young and has been primarily developed part time by myself and Sean Silva over the last ~2 months. We set it up following discussion of a Numpy/Scipy op set

> On Jun 24, 2020, at 9:53 AM, Nicolai Hähnle via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Jun 23, 2020 at 2:40 PM Stella Laurenzo via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> We originally started it as a fork of the LLVM repository, but transitioned to the MLIR standalone template, and we found it more productive to iterate out of tree in this fashion, bumping to the latest LLVM version every week or...

On Wed, Jun 24, 2020 at 9:54 AM Nicolai Hähnle <nhaehnle at gmail.com> wrote: > On Tue, Jun 23, 2020 at 2:40 PM Stella Laurenzo via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > We originally started it as a fork of the LLVM repository, but > transitioned to the MLIR standalone template, and we found it more > productive to iterate out of tree in this fashion, bumping to the latest > LLVM versio...

...r to the built-in GitHub UI and will likely keep using it (assuming no major problems). I've got comments pending on the above access request and will check in the morning. If not resolved, I'll port them to the normal GitHub UI to unblock the review. On Tue, Sep 15, 2020 at 2:48 PM Stella Laurenzo <stellaraccident at gmail.com> wrote: > I just tried it for a fairly trivial review on another project. I'll need > to do some more complex reviews with it, but my initial impressions are > quite positive. The UI is intuitive and seems "review oriented", whereas > I...

On Wed, 16 Sep 2020 at 09:37, Anton Korobeynikov via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Apparently reviewable.io requests full permissions to control the > repository and its settings. > I noticed that, too. I guess that if it wants to keep a full history of all force-rebases it may need to create sub-branches for the pull requests, as well as to approve pull

Has anyone tried out reviewable.io yet? It integrates with GitHub pull requests, but provides a separate UI for doing the review which promises to fix a lot of the issues encountered with Github's review interface. Some of the things it claims to support which seem like important additions: - Tracking the resolved status of each discussion point - Rebasing a PR without losing review history.

Hi all, Today, we maintain a high bar for getting a new subproject into LLVM: first a subproject has to be built far enough along to “prove its worth” to be part of the LLVM monorepo (e.g. demonstrate community, etc). Once conceptually approved, it needs to follow all of the policies and practices expected by an LLVM subproject. This is problematic for a couple reasons: it implicitly means that