From: Jeff Law <law@redhat.com>
To: Eric Gallager <egall@gwmail.gwu.edu>,
"Koval, Julia" <julia.koval@intel.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] remove cilk-plus
Date: Thu, 16 Nov 2017 17:59:00 -0000 [thread overview]
Message-ID: <e684659e-36ac-41d7-e62f-106ff39da9e4@redhat.com> (raw)
In-Reply-To: <CAMfHzOvQKqBw2HYD93CR9QbFYdXQ5JrxgbRU3JOKqNmmeCq3dQ@mail.gmail.com>
On 11/16/2017 09:22 AM, Eric Gallager wrote:
> On 11/16/17, Koval, Julia <julia.koval@intel.com> wrote:
>> // I failed to send patch itself, it is too big even in gzipped form. What
>> is the right way to send such big patches?
>>
>> Hi, this patch removes cilkplus. Ok for trunk?
>
> I'm not a reviewer, but just as an onlooker, I'd want to see notes
> about the removal in the caveats section of
> https://gcc.gnu.org/gcc-8/changes.html
Cilk+ was deprecated in gcc-7 and announced as-such.
But I do think a one-liner to the gcc-8 page would be appropriate to
note its removal.
Jeff
next prev parent reply other threads:[~2017-11-16 17:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 15:48 Koval, Julia
2017-11-16 15:49 ` Marek Polacek
2017-11-16 16:21 ` Jakub Jelinek
2017-11-16 17:06 ` Koval, Julia
2017-11-16 23:51 ` Joseph Myers
2017-11-21 7:46 ` Jeff Law
2017-11-22 8:47 ` Koval, Julia
2017-11-22 9:15 ` Rainer Orth
2017-11-22 9:22 ` Koval, Julia
2017-11-22 10:01 ` Koval, Julia
2017-11-22 17:33 ` Joseph Myers
2017-11-23 10:01 ` Koval, Julia
2017-11-27 18:06 ` Jeff Law
2017-11-30 11:55 ` Koval, Julia
2017-11-30 12:02 ` Jakub Jelinek
2017-11-30 16:40 ` Marek Polacek
2017-11-30 17:27 ` Jeff Law
2017-11-30 17:29 ` Jakub Jelinek
2017-11-23 17:58 ` Jeff Law
2017-11-16 16:34 ` Eric Gallager
2017-11-16 17:59 ` Jeff Law [this message]
2017-12-01 10:28 ` Paolo Carlini
2017-12-01 15:43 ` Jeff Law
2017-12-01 16:19 ` Paolo Carlini
2018-03-02 16:37 ` Thomas Schwinge
2018-03-02 16:43 ` Jeff Law
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=e684659e-36ac-41d7-e62f-106ff39da9e4@redhat.com \
--to=law@redhat.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=julia.koval@intel.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).