public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: Nathan Sidwell <nathan@acm.org>, Jakub Jelinek <jakub@redhat.com>
Cc: Cesar Philippidis <cesar@codesourcery.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: New post-LTO OpenACC pass
Date: Wed, 23 Sep 2015 13:19:00 -0000	[thread overview]
Message-ID: <5602A1EA.3060009@redhat.com> (raw)
In-Reply-To: <560297A1.8040009@acm.org>

On 09/23/2015 02:14 PM, Nathan Sidwell wrote:
> On 09/23/15 06:59, Bernd Schmidt wrote:
>> On 09/22/2015 05:16 PM, Nathan Sidwell wrote:
>>> +    if (gimple_call_builtin_p (call, BUILT_IN_ACC_ON_DEVICE))
>>> +      /* acc_on_device must be evaluated at compile time for
>>> +         constant arguments.  */
>>> +      {
>>> +        oacc_xform_on_device (call);
>>> +        rescan = true;
>>> +      }
>>
>> Is there a reason this is not done as part of pass_fold_builtins? (It
>> looks like
>> maybe adding this to fold_call_stmt in builtins.c would be sufficient
>> too).
>
> Perhaps it could be.  I'll need to check where  that pass happens.
> Anyway, the main thrust of this patch is the new pass, which I thought
> might be easier to review with minimal additional  clutter.

There's no issue adding a new pass if there's a demonstrated need for 
it, but I think builtin folding doesn't quite meet that criterion given 
that we already have a pass that does that. Unless you really need it to 
happen very early in the pipeline - fold_builtins runs pretty late, but 
I checked and fold_call_stmt gets called from pass_forwprop and possibly 
from elsewhere too.


Bernd

  reply	other threads:[~2015-09-23 12:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 16:39 Nathan Sidwell
2015-09-21 21:03 ` Cesar Philippidis
2015-09-21 21:15   ` Nathan Sidwell
2015-09-22 15:22     ` Nathan Sidwell
2015-09-23 11:10       ` Bernd Schmidt
2015-09-23 12:40         ` Nathan Sidwell
2015-09-23 13:19           ` Bernd Schmidt [this message]
2015-09-23 18:45             ` Nathan Sidwell
2015-09-23 18:58               ` Bernd Schmidt
2015-09-23 20:08                 ` Nathan Sidwell
2015-09-25  0:15                   ` Nathan Sidwell
2015-09-25 11:06                     ` Bernd Schmidt
2015-09-25 11:13                       ` Nathan Sidwell
2015-09-25 13:03                         ` Bernd Schmidt
2015-09-25 13:20                           ` Bernd Schmidt
2015-09-25 13:42                             ` Bernd Schmidt
2015-09-28 13:26                               ` Nathan Sidwell

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=5602A1EA.3060009@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=cesar@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=nathan@acm.org \
    /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).