From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128255 invoked by alias); 29 Mar 2016 15:10:30 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 127366 invoked by uid 89); 29 Mar 2016 15:10:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Committee, ultimately, igor, D*homeip.net X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 29 Mar 2016 15:10:19 +0000 Received: from svr-orw-fem-03.mgc.mentorg.com ([147.34.97.39]) by relay1.mentorg.com with esmtp id 1akvHb-0005zF-Uz from Thomas_Schwinge@mentor.com ; Tue, 29 Mar 2016 08:10:15 -0700 Received: from tftp-cs (147.34.91.1) by svr-orw-fem-03.mgc.mentorg.com (147.34.97.39) with Microsoft SMTP Server id 14.3.224.2; Tue, 29 Mar 2016 08:10:15 -0700 Received: by tftp-cs (Postfix, from userid 49978) id CB33BC1D97; Tue, 29 Mar 2016 08:10:14 -0700 (PDT) From: Thomas Schwinge To: Jeff Law , "gcc@gcc.gnu.org" CC: "Zamyatin, Igor" , "Iyer, Balaji V" , , "H.J. Lu" , Jakub Jelinek , Ilya Verbin Subject: Re: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally? In-Reply-To: <54F9E027.20002@redhat.com> References: <87r3z33g2q.fsf@kepler.schwinge.homeip.net> <54205555.5040506@redhat.com> <0EFAB2BDD0F67E4FB6CCC8B9F87D756969B792F6@IRSMSX101.ger.corp.intel.com> <871tqug0ft.fsf@kepler.schwinge.homeip.net> <20140929110019.GC17454@tucnak.redhat.com> <54F8BF10.2070701@redhat.com> <877fuvdkji.fsf@schwinge.name> <54F9E027.20002@redhat.com> User-Agent: Notmuch/0.9-125-g4686d11 (http://notmuchmail.org) Emacs/24.5.1 (i586-pc-linux-gnu) Date: Tue, 29 Mar 2016 15:10:00 -0000 Message-ID: <87zithpbg2.fsf@kepler.schwinge.homeip.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-SW-Source: 2016-03/txt/msg00240.txt.bz2 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-length: 3748 Hi! Just to remind: it had been announced in , but more than a year later, this has still not been resolved. No merge of libcilkrts has been done from the upstream Intel sources into GCC trunk (to bring in my GNU Hurd portability patches, for example). I understand that a GNU Hurd port is not of great importance, but here it seems the whole process of the Intel upstream/shared source repository is broken. Also, still nobody is listed in the GCC MAINTAINERS file as being responsible for Cilk Plus in GCC, which for more than a year, a proposal for has been pending/waiting for GCC Steering Committee approval, . Gr=C3=BC=C3=9Fe Thomas On Fri, 06 Mar 2015 10:13:11 -0700, Jeff Law wrote: > On 03/05/15 17:41, Thomas Schwinge wrote: > > On Thu, 5 Mar 2015 13:39:44 -0700, Jeff Law wrote: > >> On 02/23/15 14:41, H.J. Lu wrote: > >>> On Mon, Sep 29, 2014 at 4:00 AM, Jakub Jelinek wro= te: > >>>> On Mon, Sep 29, 2014 at 12:56:06PM +0200, Thomas Schwinge wrote: > >>>>> On Tue, 23 Sep 2014 11:02:30 +0000, "Zamyatin, Igor" wrote: > >>>>>> Jeff Law wrote: > >>>>>>> The original plan was for Balaji to take on this role; however, h= is assignment > >>>>>>> within Intel has changed and thus he's not going to have time to = work on > >>>>>>> Cilk+ anymore. > >>>>>>> > >>>>>>> Igor Zamyatin has been doing a fair amount of Cilk+ maintenance/b= ugfixing > >>>>>>> and it might make sense for him to own it in the long term if he'= s interested. > >>>>>> > >>>>>> That's right. > >>>>> > >>>>> Thanks! > >>>>> > >>>>>> Can I add 2 records (cilk plus and libcilkrts) to Various Maintain= ers section? > >>>>> > >>>>> I understand Jeff's email as a pre-approval of such a patch. > >>>> > >>>> I think only SC can appoint maintainers, and while Jeff is in the SC, > >>>> my reading of that mail wasn't that it was the SC that has acked tha= t, but > >>>> rather a question if Igor is willing to take that role, which then w= ould > >>>> need to be acked by SC. > >>> > >>> Where are we on this? Do we have a maintainer for Cilk Plus > >>> and its run-time library? > >> Not at this time. There was a bit of blockage on various things with > >> the steering committee (who approves maintainers). I've got a > >> half-dozen or so proposals queued (including Cilk maintainership). > > > > What's the process then, that I get my Cilk Plus (libcilkrts) portabili= ty > > patches committed to GCC? I was advisd this must be routed through Int= el > > (Barry M Tannenbaum CCed), which I have done months ago: I submitted the > > patches to Intel, and -- as I understood it -- Barry and I seemed to > > agree about them (at least I don't remember any requests for changes to > > be made on my side), but I have not seen a merge from Intel to update > > GCC's libcilkrts. Should I now commit to GCC the pending patches, > > > > and following? > For the runtime, the canonical bits are the upstream Cilk Plus project.=20 > So any changes for the runtime go there first. The comments WRT Cilk+= =20 > maintainers were more for the bits in GCC itself (ie, front-end=20 > extensions and related stuff up to gomp lowering/expansion. >=20 > There's the possibility of an update of the Cilk Plus runtime for gcc-5.= =20 > Igor is going to summarize the situation for the release managers to=20 > review and ultimately make a decision. >=20 > Jeff --=-=-= Content-Type: application/pgp-signature; name="signature.asc" Content-length: 472 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJW+prOAAoJEK3/DN1sMFFte3MH/A52LRPoh5R6D0iQbro/t3K0 IkE04f/h50Pfo2rs+F7Epu81ve6H4A0GyynVay/qkpWnRuhghRX1OraUvmsbJWZx +JmSC7gnBPFFtdP4mjsNoCU+nKAlAvxwoSgIs/i7ovvrxzy4oza4IkK3/DwkOIq7 1NHpARcl2j8v4niHua2ITBWw/9Yoszda33tGID6zZKxcd6N5iYhmTFdx+z4VFWcM Z3U0H1Qdie9k3mXiImqZWt6zi1RdJ65xpbhDHFaQ4HD9hijhQGo14Xl23hQ2Npjr F3/LbRIDAdYbJn+nQk7QX70cP4yktvG2ug9lBVrKLa9PfK/PwAlLzLbI+CtRo3Y= =IjR3 -----END PGP SIGNATURE----- --=-=-=--