[LLVMdev] Code Owner nominations

Evan Cheng

unread,

Nov 13, 2012, 5:59:42 PM11/13/12

to llvmdev@cs.uiuc.edu List

Hi all,

I'd recommend Andy Trick be made code owner of "instruction scheduling" (including MI, pre-RA, and post-RA schedulers). I am also recommending Nadav Rotem be made code owner of "loop vectorizer".

Evan

_______________________________________________
LLVM Developers mailing list
LLV...@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Renato Golin

unread,

Nov 13, 2012, 7:05:14 PM11/13/12

to Evan Cheng, llvmdev@cs.uiuc.edu List

On 13 November 2012 22:59, Evan Cheng <evan....@apple.com> wrote:
> Hi all,

>
> I am also recommending Nadav Rotem be made code owner of "loop vectorizer".

+1

--
cheers,
--renato

http://systemcall.org/

Chris Lattner

unread,

Nov 13, 2012, 8:54:25 PM11/13/12

to Evan Cheng, llvmdev@cs.uiuc.edu List

On Nov 13, 2012, at 2:59 PM, Evan Cheng <evan....@apple.com> wrote:

> Hi all,
>
> I'd recommend Andy Trick be made code owner of "instruction scheduling" (including MI, pre-RA, and post-RA schedulers). I am also recommending Nadav Rotem be made code owner of "loop vectorizer".

Both of those seem obvious to me. Unless there are any objections, go for it.

-Chris

Andrew Trick

unread,

Nov 14, 2012, 9:40:47 PM11/14/12

to Evan Cheng, llvmdev@cs.uiuc.edu List

On Nov 13, 2012, at 2:59 PM, Evan Cheng <evan....@apple.com> wrote:

> Hi all,
>
> I'd recommend Andy Trick be made code owner of "instruction scheduling" (including MI, pre-RA, and post-RA schedulers). I am also recommending Nadav Rotem be made code owner of "loop vectorizer".

Sergei Larin can take ownership of VLIW scheduling.

Most of the support is currently in the Hexagon target, but some framework lives in CodeGen (DFAPacketizer).

-Andy

Sergei Larin

unread,

Nov 15, 2012, 12:17:11 PM11/15/12

to Andrew Trick, Evan Cheng, llv...@cs.uiuc.edu

Thank you, Andy.

I would be happy to do so. We are on the verge of a significant code
growth for VLIW - scheduler and packetization portion of it is substantial
and essential.
Most of that framework is currently hidden in the Hexagon back end, but the
plan has always been to abstract it out into a platform independent fashion
with Hexagon being a proving ground.
Given that it makes a perfect sense to me to have a dedicated VLIW
scheduling/packetization owner, and I would be happy to do it.

Sergei

---
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
The Linux Foundation

Chris Lattner

unread,

Nov 15, 2012, 1:52:20 PM11/15/12

to Andrew Trick, llvmdev@cs.uiuc.edu List

On Nov 14, 2012, at 6:40 PM, Andrew Trick <atr...@apple.com> wrote:

>
> On Nov 13, 2012, at 2:59 PM, Evan Cheng <evan....@apple.com> wrote:
>
>> Hi all,
>>
>> I'd recommend Andy Trick be made code owner of "instruction scheduling" (including MI, pre-RA, and post-RA schedulers). I am also recommending Nadav Rotem be made code owner of "loop vectorizer".
>
>
> Sergei Larin can take ownership of VLIW scheduling.
>
> Most of the support is currently in the Hexagon target, but some framework lives in CodeGen (DFAPacketizer).

Sounds great, please update CODE_OWNERS.

-Chris

Reply all

Reply to author

Forward