Mehdi AMINI via llvm-dev
2021-Jan-27 18:51 UTC
[llvm-dev] RFC: Enzyme, Automatic Differentiation for LLVM as an LLVM Incubator Project
On Wed, Jan 27, 2021 at 4:05 AM Renato Golin <rengolin at gmail.com> wrote:> On Tue, 26 Jan 2021 at 22:51, William Moses <wmoses at mit.edu> wrote: > >> Since it seems like all of the feedback here is positive, what would be >> the next steps (migrate Enzyme mailing list to LLVM, create >> discord/discourse, etc)? >> > > I wouldn't worry about merging the lists too soon (very high traffic). > MLIR has a separate channel and that seems to be working for them, you > could follow their path at least for now. > > I couldn't find the code's license, but since you're working with MIT, I > imagine it's compatible (and convertible) to the LLVM license. Everything > else checks for me, including the migration plan towards the monorepo. > > Mehdi, does that answer your questions? >Yes, sorry I didn't follow up but William's answer was perfectly fine with me. First step will be to get a repo on github in the LLVM project, we can setup a phabricator project to track it if needed (other incubator projects are using pull-requests). After that a subsection in the incubator category with the others there: https://llvm.discourse.group and similar on Discord is fairly straightforward.> > Should we look for more people to have a look and comment? Alex, perhaps > mentioning on the weekly again next week to see if we get more people to > look at it? >Yes that'd be great to have more people chime in and express some support on this!> > Regarding Enzyme/MLIR, the idea there isn't necessarily to use Enzyme to >> differentiate MLIR directly, but lowering MLIR to LLVM then running Enzyme >> could be an interesting (though not necessarily ideal) way to provide >> differentiable programming in MLIR. We're also considering extending Enzyme >> to work directly on MLIR as well and while indeed many parts of the >> analysis are specific to LLVM instructions, other differentiation specific >> analyses likely will have components which can be shared (e.g. Activity >> Analysis which determines whether there exists a path through the program >> that enables differentiable information to flow from input to output). >> > > MLIR doesn't always goes to LLVM IR, that's why I suggested it. >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210127/6c8869a1/attachment.html>
Johannes Doerfert via llvm-dev
2021-Jan-27 19:29 UTC
[llvm-dev] RFC: Enzyme, Automatic Differentiation for LLVM as an LLVM Incubator Project
On 1/27/21 12:51 PM, Mehdi AMINI via llvm-dev wrote:> On Wed, Jan 27, 2021 at 4:05 AM Renato Golin <rengolin at gmail.com> wrote: > >> On Tue, 26 Jan 2021 at 22:51, William Moses <wmoses at mit.edu> wrote: >> >>> Since it seems like all of the feedback here is positive, what would be >>> the next steps (migrate Enzyme mailing list to LLVM, create >>> discord/discourse, etc)? >>> >> I wouldn't worry about merging the lists too soon (very high traffic). >> MLIR has a separate channel and that seems to be working for them, you >> could follow their path at least for now.I think the idea was `enzyme-dev at lists.llvm.org` not merging the lists ;)>> >> Should we look for more people to have a look and comment? Alex, perhaps >> mentioning on the weekly again next week to see if we get more people to >> look at it? >> > Yes that'd be great to have more people chime in and express some support > on this! >+1> >> Regarding Enzyme/MLIR, the idea there isn't necessarily to use Enzyme to >>> differentiate MLIR directly, but lowering MLIR to LLVM then running Enzyme >>> could be an interesting (though not necessarily ideal) way to provide >>> differentiable programming in MLIR. We're also considering extending Enzyme >>> to work directly on MLIR as well and while indeed many parts of the >>> analysis are specific to LLVM instructions, other differentiation specific >>> analyses likely will have components which can be shared (e.g. Activity >>> Analysis which determines whether there exists a path through the program >>> that enables differentiable information to flow from input to output). >>> >> MLIR doesn't always goes to LLVM IR, that's why I suggested it. >> > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev