From: Xi Ruoyao <ryxi@stu.xidian.edu.cn>
To: Jeff Law <law@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
Jan Hubicka <hubicka@ucw.cz>
Cc: ryxi@stu.xidian.edu.cn, GCC Patches <gcc-patches@gcc.gnu.org>,
Florent Hivert <florent.hivert@lri.fr>
Subject: Re: [PATCH] Destroy arguments for _Cilk_spawn calling in the child (PR 80038)
Date: Fri, 28 Apr 2017 14:51:00 -0000 [thread overview]
Message-ID: <1493389879.9757.3.camel@stu.xidian.edu.cn> (raw)
In-Reply-To: <60054e41-6470-40c7-ed8b-7b05862f5969@redhat.com>
On 2017-04-25 09:30 -0600, Jeff Law wrote:
> Given Richi's general agreement around the in_lto_p, let's go with theÂ
> patch on the trunk only.
Should I prepare (re-diff) a patch for current trunk?
> If you get positive feedback from Jan, then this can be backported toÂ
> gcc-7 after it's been on the trunk for at least a week.
>
I just noticed GCC 7.0 has been frozen.
--
Xi Ruoyao <ryxi@stu.xidian.edu.cn>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2017-04-28 14:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 13:58 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 [this message]
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
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=1493389879.9757.3.camel@stu.xidian.edu.cn \
--to=ryxi@stu.xidian.edu.cn \
--cc=florent.hivert@lri.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=richard.guenther@gmail.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).