public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Ilya Verbin <iverbin@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ptx] partitioning optimization
Date: Wed, 11 Nov 2015 13:37:00 -0000	[thread overview]
Message-ID: <56434490.9030806@acm.org> (raw)
In-Reply-To: <CADG=Z0Gh0EcBFr2m39Vnptzix+nOC=0a_SAxUpR+5_YBQqFnDQ@mail.gmail.com>

On 11/10/15 17:45, Ilya Verbin wrote:
>> I've been unable to introduce a testcase for this. The difficulty is we want
>> to check an rtl dump from the acceleration compiler, and there doesn't
>> appear to be existing machinery for that in the testsuite.  Perhaps
>> something to be added later?
>
> I haven't tried it, but doesn't
> /* { dg-options "-foffload=-fdump-rtl-..." } */
> with
> /* { dg-final { scan-rtl-dump ... } } */
> work?

in the gcc testsuite directories?  That's the approach I was going for.

The issue is detecting when the test should be run.  target==nvptx-*-* isn't 
right, as the target is the x86 host machine.  There doesn't seem to be an 
existing dejagnu predicate there to select for 'accel_target==FOO'.  Am I 
missing something?

nathan

  reply	other threads:[~2015-11-11 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 12:33 [gomp4] loop partition optimization Nathan Sidwell
2015-11-10 22:34 ` [ptx] partitioning optimization Nathan Sidwell
2015-11-10 22:45   ` Ilya Verbin
2015-11-11 13:37     ` Nathan Sidwell [this message]
2015-11-11 12:06   ` Bernd Schmidt
2015-11-11 13:59     ` Nathan Sidwell
2015-11-11 14:19       ` Bernd Schmidt
2015-11-13 20:07         ` Nathan Sidwell
2015-11-13 20:22           ` Bernd Schmidt
2015-11-23  7:47             ` Thomas Schwinge
2015-11-23  8:46               ` Jakub Jelinek
2015-11-11 17:16       ` Thomas Schwinge

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=56434490.9030806@acm.org \
    --to=nathan@acm.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iverbin@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).