public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Xi Ruoyao <ryxi@stu.xidian.edu.cn>, Andreas Schwab <schwab@suse.de>
Cc: Richard Biener <richard.guenther@gmail.com>,
	Jan Hubicka <hubicka@ucw.cz>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Florent Hivert <florent.hivert@lri.fr>
Subject: Re: [PATCH v2] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)
Date: Tue, 02 May 2017 15:45:00 -0000	[thread overview]
Message-ID: <312bbefa-0bb2-f142-9fa4-a77e2a5c382f@redhat.com> (raw)
In-Reply-To: <1493711779.24177.3.camel@stu.xidian.edu.cn>

On 05/02/2017 01:56 AM, Xi Ruoyao wrote:
> On 2017-05-02 09:16 +0200, Andreas Schwab wrote:
> 
>> This could be related to --enable-checking=release:
>>
>> In file included from ../../gcc/c-family/c-common.h:26:0,
>>                   from ../../gcc/c-family/cilk.c:28:
>> ../../gcc/c-family/cilk.c: In function 'bool cilk_set_spawn_marker(location_t, tree)':
>> ../../gcc/tree.h:901:42: error: 'tree_check2' was not declared in this scope
>>                   CALL_EXPR, AGGR_INIT_EXPR)->base.u.bits.unsigned_flag)
>>                                            ^
>> ../../gcc/c-family/cilk.c:113:9: note: in expansion of macro 'EXPR_CILK_SPAWN'
>>           EXPR_CILK_SPAWN (fcall) = 1;
>>           ^
>> ../../gcc/tree.h:901:42: error: 'tree_check2' was not declared in this scope
>>                   CALL_EXPR, AGGR_INIT_EXPR)->base.u.bits.unsigned_flag)
>>                                            ^
>> ../../gcc/c-family/cilk.c:115:9: note: in expansion of macro 'EXPR_CILK_SPAWN'
>>           EXPR_CILK_SPAWN (TREE_OPERAND (fcall, 1)) = 1;
>>           ^
>>
>> Andreas.
>>
> 
> Sorry T_T.  I've made a stupid mistake in tree.h.
> 
> Let's apply following patch, and alert the RM when backporting r247446.
> 
> 2017-05-02 Xi Ruoyao <ryxi@stu.xidian.edu.cn>
> 
> 	* tree.h (EXPR_CILK_SPAWN): Use macro TREE_CHECK2 instead of
> 	function tree_check2.
THanks.  Installed.

jeff

  reply	other threads:[~2017-05-02 15:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 13:58 [PATCH] " Xi Ruoyao
2017-04-06 17:12 ` Jeff Law
2017-04-07 14:03   ` Xi Ruoyao
2017-04-12 21:17     ` Jeff Law
2017-04-13  7:05       ` Richard Biener
2017-04-14  7:00         ` Xi Ruoyao
2017-04-15  4:05           ` Xi Ruoyao
2017-04-25 15:37             ` Jeff Law
2017-04-28 14:51               ` Xi Ruoyao
2017-04-28 15:29                 ` Jeff Law
2017-04-29  8:51                   ` [PATCH v2] " Xi Ruoyao
2017-05-01 22:26                     ` Jeff Law
2017-05-02  7:56                       ` Andreas Schwab
2017-05-02  8:18                         ` Xi Ruoyao
2017-05-02 15:45                           ` Jeff Law [this message]
2017-08-21 17:33               ` [PATCH, gcc-7-branch] Backport PR80038 Xi Ruoyao
2017-08-21 17:46                 ` Xi Ruoyao
2017-08-22  9:04                   ` Richard Biener
2017-08-24 13:06                     ` Xi Ruoyao
2017-09-06  4:33                       ` Xi Ruoyao

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=312bbefa-0bb2-f142-9fa4-a77e2a5c382f@redhat.com \
    --to=law@redhat.com \
    --cc=florent.hivert@lri.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=richard.guenther@gmail.com \
    --cc=ryxi@stu.xidian.edu.cn \
    --cc=schwab@suse.de \
    /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).