From: Ilya Verbin <iverbin@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Kirill Yukhin <kirill.yukhin@gmail.com>
Subject: Re: [PATCH][CilkPlus] Allow parenthesized initialization in for-loops
Date: Tue, 10 May 2016 19:29:00 -0000 [thread overview]
Message-ID: <20160510192828.GD47195@msticlxl57.ims.intel.com> (raw)
In-Reply-To: <20160325152323.GA61128@msticlxl57.ims.intel.com>
On Fri, Mar 25, 2016 at 18:23:23 +0300, Ilya Verbin wrote:
> On Mon, Mar 21, 2016 at 15:58:18 +0100, Jakub Jelinek wrote:
> > On Mon, Mar 21, 2016 at 05:45:52PM +0300, Ilya Verbin wrote:
> > > www.cilkplus.org/sites/default/files/open_specifications/Intel_Cilk_plus_lang_spec_1.2.htm
> > > says:
> > > In C++, the control variable shall be declared and initialized within the
> > > initialization clause of the _Cilk_for loop. The variable shall have automatic
> > > storage duration. The variable shall be initialized. Initialization may be
> > > explicit, using assignment or constructor syntax, or implicit via a nontrivial
> > > default constructor.
> > >
> > > This patch enables constructor-syntax initialization.
> > > Bootstraped and regtested on x86_64-linux. OK for stage1?
> >
> > Does this affect just _Cilk_for or also #pragma simd?
>
> It affects both.
>
> > What about (some_class i { 0 }; some_class < ...; some_class++)
> > and similar syntax?
>
> It's allowed, thanks, I missed this in the initial patch.
>
> > The testsuite coverage is insufficient (nothing e.g.
> > tests templates or #pragma simd).
>
> Patch is updated. Is it sufficient now?
>
>
> gcc/cp/
> * parser.c (cp_parser_omp_for_loop_init): Allow constructor syntax in
> Cilk Plus for-loop initialization.
> gcc/testsuite/
> * g++.dg/cilk-plus/CK/for2.cc: New test.
> * g++.dg/cilk-plus/for5.C: New test.
Ping.
-- Ilya
next prev parent reply other threads:[~2016-05-10 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 14:49 Ilya Verbin
2016-03-21 15:01 ` Jakub Jelinek
2016-03-25 16:16 ` Ilya Verbin
2016-05-10 19:29 ` Ilya Verbin [this message]
2016-05-19 14:36 ` Jason Merrill
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=20160510192828.GD47195@msticlxl57.ims.intel.com \
--to=iverbin@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@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).