public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Zamyatin, Igor" <igor.zamyatin@intel.com>
To: "Tannenbaum, Barry M" <barry.m.tannenbaum@intel.com>,
	Thomas Schwinge	<thomas@codesourcery.com>,
	Jeff Law <law@redhat.com>
Cc: "Iyer, Balaji V" <balaji.v.iyer@intel.com>,
	"gcc@gcc.gnu.org"	<gcc@gcc.gnu.org>,
	"H.J. Lu" <hjl.tools@gmail.com>, Jakub Jelinek	<jakub@redhat.com>,
	"Bae, Hansang" <hansang.bae@intel.com>
Subject: RE: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally?
Date: Fri, 06 Mar 2015 14:37:00 -0000	[thread overview]
Message-ID: <0EFAB2BDD0F67E4FB6CCC8B9F87D756969E255C1@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <6B86B7F2A4026246AA81BA1ABF9756906A6C29A1@fmsmsx107.amr.corp.intel.com>

> I apologize. They got caught up in other issues. They've been merged into
> our mainstream and I believe they were just posted to the cilkplus.org
> website and submitted to GCC.

I'm going to submit latest cilk runtime sources next week so I will check the mentioned change.

Thanks,
Igor

> 
>   - Barry
> 
> -----Original Message-----
> From: Thomas Schwinge [mailto:thomas@codesourcery.com]
> Sent: Thursday, March 5, 2015 7:42 PM
> To: Jeff Law
> Cc: Zamyatin, Igor; Iyer, Balaji V; gcc@gcc.gnu.org; Tannenbaum, Barry M;
> H.J. Lu; Jakub Jelinek
> Subject: Re: Listing a maintainer for libcilkrts, and GCC's Cilk Plus
> implementation generally?
> 
> Hi!
> 
> On Thu, 5 Mar 2015 13:39:44 -0700, Jeff Law <law@redhat.com> wrote:
> > On 02/23/15 14:41, H.J. Lu wrote:
> > > On Mon, Sep 29, 2014 at 4:00 AM, Jakub Jelinek <jakub@redhat.com>
> wrote:
> > >> On Mon, Sep 29, 2014 at 12:56:06PM +0200, Thomas Schwinge wrote:
> > >>> On Tue, 23 Sep 2014 11:02:30 +0000, "Zamyatin, Igor"
> <igor.zamyatin@intel.com> wrote:
> > >>>> Jeff Law wrote:
> > >>>>> The original plan was for Balaji to take on this role; however,
> > >>>>> his 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/bugfixing 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 Maintainers
> 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 that, but rather a question if Igor is willing to take that
> > >> role, which then would 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) portability patches
> committed to GCC?  I was advisd this must be routed through Intel (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, <http://news.gmane.org/find-
> root.php?message_id=%3C8738bae1mp.fsf%40kepler.schwinge.homeip.net
> %3E>
> and following?
> 
> 
> Grüße,
>  Thomas

  reply	other threads:[~2015-03-06 14:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 14:06 Thomas Schwinge
2014-09-22 14:35 ` Make name+email address cut'n'paste-able (was: Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally?) Jan-Benedict Glaw
2014-09-22 16:42   ` Make name+email address cut'n'paste-able Jeff Law
2014-09-22 17:08 ` Listing a maintainer for libcilkrts, and GCC's Cilk Plus implementation generally? Jeff Law
2014-09-23 11:18   ` Zamyatin, Igor
2014-09-29 11:00     ` Thomas Schwinge
2014-09-29 11:09       ` Jakub Jelinek
2014-09-29 13:10         ` Thomas Schwinge
2015-02-23 21:41         ` H.J. Lu
2015-03-05 20:39           ` Jeff Law
2015-03-06  0:42             ` Thomas Schwinge
2015-03-06 14:26               ` Tannenbaum, Barry M
2015-03-06 14:37                 ` Zamyatin, Igor [this message]
2015-03-06 17:13               ` Jeff Law
2016-03-29 15:10                 ` Thomas Schwinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0EFAB2BDD0F67E4FB6CCC8B9F87D756969E255C1@IRSMSX101.ger.corp.intel.com \
    --to=igor.zamyatin@intel.com \
    --cc=balaji.v.iyer@intel.com \
    --cc=barry.m.tannenbaum@intel.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hansang.bae@intel.com \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=law@redhat.com \
    --cc=thomas@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).