This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)
- From: Jeff Law <law at redhat dot com>
- To: Xi Ruoyao <ryxi at stu dot xidian dot edu dot cn>, gcc-patches at gcc dot gnu dot org
- Cc: Florent Hivert <florent dot hivert at lri dot fr>
- Date: Thu, 6 Apr 2017 11:12:37 -0600
- Subject: Re: [PATCH] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=law at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com AE6F061D37
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com AE6F061D37
- References: <1490968216.19897.36.camel@stu.xidian.edu.cn>
On 03/31/2017 07:50 AM, Xi Ruoyao wrote:
Hi,
I''ve sent this patch once (<https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01261.html>).
But I haven't got any response. I'd like to resend it instead of pinging, and explain it more.
There's a couple things going on here. Cilk+ does not currently have a
maintainer, thus review of Cilk+ changes can easily fall through the
cracks. Additionally, the plan is deprecate Cilk+ in gcc-7, so it's
very very low on our priority list.
With the likely deprecation in mind, I've only done a cursory review of
the changes -- mostly to verify that they hit Cilk+ paths only.
What's the purpose behind changing when we set the in_lto_p flag?
Jeff