From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jeff Law <law@redhat.com>, "Koval, Julia" <julia.koval@intel.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] remove cilk-plus
Date: Fri, 01 Dec 2017 16:19:00 -0000 [thread overview]
Message-ID: <9045169e-aea5-eea0-f14c-c57b5c429332@oracle.com> (raw)
In-Reply-To: <b7d69879-aeaa-97af-cd2d-fbe2f3859386@redhat.com>
Hi,
On 01/12/2017 16:43, Jeff Law wrote:
> On 12/01/2017 03:28 AM, Paolo Carlini wrote:
>> Hi,
>>
>> On 16/11/2017 16:33, Koval, Julia 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?
>> Now that cilkplus is gone I suppose we should clean-up Bugzilla about
>> that. Shall I go ahead and essentially close all the bugs we got? As
>> WONTFIX or what else? Let's agree on something. In principle we could
>> keep the regressions for the sake of the existing release branches but I
>> think we got very, very, few of those and anyway I don't see who gonna
>> work on that...
> Not sure if we have a policy in this space or not.
>
> If we don't then my vote would be for CLOSE/WONTFIX now. That seems to
> most accurately reflect state -- we're not going to be fixing any Cilk+
> stuff on the trunk or in the release branches.
Excellent, thanks Jeff. Thus, barring strong contrary opinions, I'll
take care of that over the we.
Cheers,
Paolo.
next prev parent reply other threads:[~2017-12-01 16:19 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
2017-12-01 10:28 ` Paolo Carlini
2017-12-01 15:43 ` Jeff Law
2017-12-01 16:19 ` Paolo Carlini [this message]
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=9045169e-aea5-eea0-f14c-c57b5c429332@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=julia.koval@intel.com \
--cc=law@redhat.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).