public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ilya Verbin <iverbin@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, "Zamyatin,
	Igor" <igor.zamyatin@intel.com>,
	Kirill Yukhin <kirill.yukhin@gmail.com>,
	barry.m.tannenbaum@intel.com, Jakub Jelinek <jakub@redhat.com>
Subject: Re: FW: [PATCH] Cilk Keywords (_Cilk_spawn and _Cilk_sync) for C
Date: Tue, 29 Mar 2016 16:19:00 -0000	[thread overview]
Message-ID: <20160329153058.GB52596@msticlxl57.ims.intel.com> (raw)
In-Reply-To: <87y491pb7k.fsf@kepler.schwinge.homeip.net>

On Tue, Mar 29, 2016 at 17:15:11 +0200, Thomas Schwinge wrote:
> On Mon, 28 Mar 2016 19:40:22 +0300, Ilya Verbin <iverbin@gmail.com> wrote:
> > Do you plan to commit this patch? :)
> 
> Well, I'm also still waiting for you guys to merge (via the upstream
> Intel sources repository) my GNU Hurd portability patches; submitted to
> GCC in
> <http://news.gmane.org/find-root.php?message_id=%3C8738bae1mp.fsf%40kepler.schwinge.homeip.net%3E>
> and the following messages, dated 2014-09-26.  Upon request of Barry M
> Tannenbaum then submitted to the Intel web site, and then never heard of
> again...  ;-(

I'm going to merge libcilkrts from upstream at stage1.  Your patch is there:
https://bitbucket.org/intelcilkruntime/intel-cilk-runtime/commits/2b33a7bfcbcd1def8108287475755b68b4aef2f7

  -- Ilya

  reply	other threads:[~2016-03-29 15:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 20:48 Iyer, Balaji V
2013-08-06 16:49 ` Aldy Hernandez
2013-08-06 17:04   ` Richard Henderson
2013-08-08 19:33   ` Iyer, Balaji V
2013-08-09 10:40     ` Aldy Hernandez
2013-08-13 20:32       ` Iyer, Balaji V
2013-08-19 22:24         ` Aldy Hernandez
2013-08-21 23:08           ` Iyer, Balaji V
2013-08-20 22:28         ` Aldy Hernandez
2013-08-21  4:35           ` Iyer, Balaji V
2013-08-21 15:49         ` Aldy Hernandez
2013-08-21 19:21           ` Jeff Law
2013-08-21 20:02           ` Iyer, Balaji V
2013-08-22 16:53             ` Aldy Hernandez
2013-08-27 22:29               ` FW: " Iyer, Balaji V
2014-09-22 13:57                 ` Thomas Schwinge
2014-09-22 19:28                   ` Tannenbaum, Barry M
2014-09-29 10:54                     ` Thomas Schwinge
2014-09-29 13:59                       ` Tannenbaum, Barry M
2014-09-29 14:26                         ` Thomas Schwinge
2014-09-29 14:56                           ` Tannenbaum, Barry M
2014-09-29 15:24                           ` Jeff Law
2016-03-28 18:05                             ` Ilya Verbin
2016-03-29 16:02                               ` Thomas Schwinge
2016-03-29 16:19                                 ` Ilya Verbin [this message]
     [not found]               ` <BF230D13CA30DD48930C31D4099330003A45D42C@FMSMSX101.amr.corp.intel.com>
2013-08-28 18:38                 ` Aldy Hernandez
2013-08-30 17:02                   ` FW: " Iyer, Balaji V
     [not found]                   ` <BF230D13CA30DD48930C31D4099330003A45F32A@FMSMSX101.amr.corp.intel.com>
2013-09-02 13:10                     ` Aldy Hernandez
2013-08-09 16:52     ` Joseph S. Myers
2013-08-13 20:33       ` Iyer, Balaji V

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=20160329153058.GB52596@msticlxl57.ims.intel.com \
    --to=iverbin@gmail.com \
    --cc=barry.m.tannenbaum@intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=igor.zamyatin@intel.com \
    --cc=jakub@redhat.com \
    --cc=kirill.yukhin@gmail.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).