public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Bernd Schmidt <bschmidt@redhat.com>, 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 20:08:00 -0000	[thread overview]
Message-ID: <5602F662.6000202@acm.org> (raw)
In-Reply-To: <5602F4BB.9000908@redhat.com>

On 09/23/15 14:51, Bernd Schmidt wrote:
> On 09/23/2015 08:42 PM, Nathan Sidwell wrote:
>
>> As I feared, builtin folding occurs in several places.  In particular
>> its first call is very early on in the host compiler, which is far too
>> soon.
>>
>> We have to defer folding until we know whether we're doing host or
>> device compilation.
>
> Doesn't something like "symtab->state >= EXPANSION" give you that?

I don't know.   It doesn't seem to me to be a good idea for the builtin 
expanders to be context-sensitive.

nathan

  reply	other threads:[~2015-09-23 18: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
2015-09-23 18:45             ` Nathan Sidwell
2015-09-23 18:58               ` Bernd Schmidt
2015-09-23 20:08                 ` Nathan Sidwell [this message]
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=5602F662.6000202@acm.org \
    --to=nathan@acm.org \
    --cc=bschmidt@redhat.com \
    --cc=cesar@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@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).