It been a while since I worked on the vectorizers and I think that it's time for someone else to be the code owner. During the conference I talked about this with Arnold and a few other people who were involved in the development of the vectorizers. Based on these discussions I recommend Michael Kuperstein. Michael is committed to improving LLVM and has lots of relevant experience. If approved by the community, I know he would do a great job working with contributors on improving the vectorizers and reviewing the recent proposals from ARM and Intel. -Nadav -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161106/8d3738a6/attachment.html>
Michael seems a great choice, +1 from me! On Sun, 6 Nov 2016 at 06:00 Nadav Rotem via llvm-dev < llvm-dev at lists.llvm.org> wrote:> It been a while since I worked on the vectorizers and I think that it's > time for someone else to be the code owner. During the conference I talked > about this with Arnold and a few other people who were involved in the > development of the vectorizers. Based on these discussions I recommend > Michael Kuperstein. Michael is committed to improving LLVM and has lots of > relevant experience. If approved by the community, I know he would do a > great job working with contributors on improving the vectorizers and > reviewing the recent proposals from ARM and Intel. > > -Nadav > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161106/551325e2/attachment.html>
+1 On 6 Nov 2016 05:53, "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> wrote:> Michael seems a great choice, +1 from me! > > On Sun, 6 Nov 2016 at 06:00 Nadav Rotem via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> It been a while since I worked on the vectorizers and I think that it's >> time for someone else to be the code owner. During the conference I talked >> about this with Arnold and a few other people who were involved in the >> development of the vectorizers. Based on these discussions I recommend >> Michael Kuperstein. Michael is committed to improving LLVM and has lots of >> relevant experience. If approved by the community, I know he would do a >> great job working with contributors on improving the vectorizers and >> reviewing the recent proposals from ARM and Intel. >> >> -Nadav >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161106/f90b1b73/attachment-0001.html>
Even though I moved out of the vector land for now. looks like a great choice to me! Sergei From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Nadav Rotem via llvm-dev Sent: Sunday, November 06, 2016 1:00 AM To: llvm-dev at lists.llvm.org Subject: [llvm-dev] Vectorizers code ownership It been a while since I worked on the vectorizers and I think that it's time for someone else to be the code owner. During the conference I talked about this with Arnold and a few other people who were involved in the development of the vectorizers. Based on these discussions I recommend Michael Kuperstein. Michael is committed to improving LLVM and has lots of relevant experience. If approved by the community, I know he would do a great job working with contributors on improving the vectorizers and reviewing the recent proposals from ARM and Intel. -Nadav -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161107/bf8bcb05/attachment.html>
I think Michael would be an excellent code owner. +1 On 2016-11-06 01:00, Nadav Rotem via llvm-dev wrote:> It been a while since I worked on the vectorizers and I think that > it's time for someone else to be the code owner. During the conference > I talked about this with Arnold and a few other people who were > involved in the development of the vectorizers. Based on these > discussions I recommend Michael Kuperstein. Michael is committed to > improving LLVM and has lots of relevant experience. If approved by the > community, I know he would do a great job working with contributors on > improving the vectorizers and reviewing the recent proposals from ARM > and Intel. > > -Nadav > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
+1 On Mon, Nov 7, 2016 at 8:31 AM, via llvm-dev <llvm-dev at lists.llvm.org> wrote:> I think Michael would be an excellent code owner. +1 > > > On 2016-11-06 01:00, Nadav Rotem via llvm-dev wrote: >> >> It been a while since I worked on the vectorizers and I think that >> it's time for someone else to be the code owner. During the conference >> I talked about this with Arnold and a few other people who were >> involved in the development of the vectorizers. Based on these >> discussions I recommend Michael Kuperstein. Michael is committed to >> improving LLVM and has lots of relevant experience. If approved by the >> community, I know he would do a great job working with contributors on >> improving the vectorizers and reviewing the recent proposals from ARM >> and Intel. >> >> -Nadav >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-- Sanjoy Das http://playingwithpointers.com
> On Nov 5, 2016, at 11:00 PM, Nadav Rotem via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > It been a while since I worked on the vectorizers and I think that it's time for someone else to be the code owner. During the conference I talked about this with Arnold and a few other people who were involved in the development of the vectorizers. Based on these discussions I recommend Michael Kuperstein. Michael is committed to improving LLVM and has lots of relevant experience. If approved by the community, I know he would do a great job working with contributors on improving the vectorizers and reviewing the recent proposals from ARM and Intel.Makes sense to me too! Michael, assuming no strong objection in the next 24 hours, please update CODE_OWNERS.txt. Congrats! Also, thank you for your long service in this area Nadav, -Chris
On 7 November 2016 at 10:36, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:> Also, thank you for your long service in this area Nadav,+10!
+1 -- Matt On Sun, Nov 6, 2016 at 1:00 AM, Nadav Rotem via llvm-dev < llvm-dev at lists.llvm.org> wrote:> It been a while since I worked on the vectorizers and I think that it's > time for someone else to be the code owner. During the conference I talked > about this with Arnold and a few other people who were involved in the > development of the vectorizers. Based on these discussions I recommend > Michael Kuperstein. Michael is committed to improving LLVM and has lots of > relevant experience. If approved by the community, I know he would do a > great job working with contributors on improving the vectorizers and > reviewing the recent proposals from ARM and Intel. > > -Nadav > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161107/92881084/attachment.html>
+1 Thanks Nadav for your help over the last few years! Andrea On Mon, Nov 7, 2016 at 9:20 PM, Matthew Simpson via llvm-dev < llvm-dev at lists.llvm.org> wrote:> +1 > > -- Matt > > On Sun, Nov 6, 2016 at 1:00 AM, Nadav Rotem via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> It been a while since I worked on the vectorizers and I think that it's >> time for someone else to be the code owner. During the conference I talked >> about this with Arnold and a few other people who were involved in the >> development of the vectorizers. Based on these discussions I recommend >> Michael Kuperstein. Michael is committed to improving LLVM and has lots of >> relevant experience. If approved by the community, I know he would do a >> great job working with contributors on improving the vectorizers and >> reviewing the recent proposals from ARM and Intel. >> >> -Nadav >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> >> > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161108/b24b6c58/attachment-0001.html>
Hi Nadav, What about your code ownership on the X86 backend? Simon Pilgrim, Sanjay Patel, and a few others have been very active on that backend if you are looking for a replacement. Cheers, -Quentin> On Nov 5, 2016, at 11:00 PM, Nadav Rotem via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > It been a while since I worked on the vectorizers and I think that it's time for someone else to be the code owner. During the conference I talked about this with Arnold and a few other people who were involved in the development of the vectorizers. Based on these discussions I recommend Michael Kuperstein. Michael is committed to improving LLVM and has lots of relevant experience. If approved by the community, I know he would do a great job working with contributors on improving the vectorizers and reviewing the recent proposals from ARM and Intel. > > -Nadav > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev