public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Ryan Burn <ryan.burn@gmail.com>,
	gcc-patches@gcc.gnu.org, jason@redhat.com
Cc: igor.zamyatin@intel.com
Subject: Re: [PATCH] fix gimplification of call parameters (PR cilkplus/69267)
Date: Wed, 27 Jan 2016 17:19:00 -0000	[thread overview]
Message-ID: <56A8FC07.5070607@redhat.com> (raw)
In-Reply-To: <8335D685-ADCD-4DEA-8AD2-DA3A1B100A1F@gmail.com>

On 01/15/2016 03:41 PM, Ryan Burn wrote:
> 2016-01-15  Ryan Burn<contact@rnburn.com>
>
>          PR cilkplus/69267
>          * cilk.c (cilk_gimplify_call_params_in_spawned_fn): Change to use
>          gimplify_arg. Removed superfluous post_p argument.
>          * c-family.h (cilk_gimplify_call_params_in_spawned_fn): Removed
>          superfluous post_p argument.
>          * c-gimplify.c (c_gimplify_expr): Likewise.
>
> gcc/cp/ChangeLog:
>
> 2016-01-15  Ryan Burn<contact@rnburn.com>
>
>          PR cilkplus/69267
>          * cp-gimplify.c (cilk_cp_gimplify_call_params_in_spawned_fn): Removed
>          superfluous post_p argument in call to
>          cilk_gimplify_call_params_in_spawned_fn.
>
> gcc/testsuite/ChangeLog:
>
> 2016-01-15  Ryan Burn<contact@rnburn.com>
>
> PR cilkplus/69267
> * g++.dg/cilk-plus/CK/pr69267.cc: New test.
>
Thanks.  Even though we're in stage4, this came in before stage3 closed. 
  I went ahead and committed it to the trunk.

Thanks again, and sorry about the delay.

jeff

      parent reply	other threads:[~2016-01-27 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 22:41 Ryan Burn
2016-01-19 14:28 ` Ryan Burn
2016-01-25 15:15   ` Ryan Burn
2016-01-27 17:19 ` Jeff Law [this message]

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=56A8FC07.5070607@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=igor.zamyatin@intel.com \
    --cc=jason@redhat.com \
    --cc=ryan.burn@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).