From: "Koval, Julia" <julia.koval@intel.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Jeff Law <law@redhat.com>, Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: RE: [patch] remove cilk-plus
Date: Thu, 23 Nov 2017 10:01:00 -0000 [thread overview]
Message-ID: <4E89A029A0F8D443B436A5167BA3C53F42AD4D90@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1711221721240.30870@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Sorry, I think in this version of this patch they are fixed.
> -----Original Message-----
> From: Joseph Myers [mailto:joseph@codesourcery.com]
> Sent: Wednesday, November 22, 2017 6:23 PM
> To: Koval, Julia <julia.koval@intel.com>
> Cc: Jeff Law <law@redhat.com>; Jakub Jelinek <jakub@redhat.com>; GCC
> Patches <gcc-patches@gcc.gnu.org>
> Subject: RE: [patch] remove cilk-plus
>
> This patch version does not appear to address my comment that you're
> leaving behind comments in c-parser.c relating to Cilk array notations
> while removing the subsequent code. (Or in one case actually reindenting
> the comment that is no longer relevant, rather than removing it.)
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
[-- Attachment #2: cilk-plus.tar.xz --]
[-- Type: application/octet-stream, Size: 82132 bytes --]
next prev parent reply other threads:[~2017-11-23 9:45 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 [this message]
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
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=4E89A029A0F8D443B436A5167BA3C53F42AD4D90@IRSMSX101.ger.corp.intel.com \
--to=julia.koval@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).