From: Thomas Schwinge <thomas@codesourcery.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Ilya Verbin <iverbin@gmail.com>
Subject: Re: [ptx] partitioning optimization
Date: Wed, 11 Nov 2015 17:16:00 -0000 [thread overview]
Message-ID: <8737wcv4lg.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <564349B5.5050202@acm.org>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
Hi!
On Wed, 11 Nov 2015 08:59:17 -0500, Nathan Sidwell <nathan@acm.org> wrote:
> On 11/11/15 07:06, Bernd Schmidt wrote:
> > On 11/10/2015 11:33 PM, Nathan Sidwell wrote:
> >> I've been unable to introduce a testcase for this.
(But you still committed an update to gcc/testsuite/ChangeLog.)
You'll need to put such an offloading test into the libgomp testsuite --
offloading complation requires linking, and during that, the offloading
compiler(s) will be invoked, which only the libgomp testsuite is set up
to do, as discussed before.
> >> 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?
> >
> > What's the difficulty exactly? Getting a dump should be possible with
> > -foffload=-fdump-whatever, does the testsuite have a problem finding the right
> > filename?
Currently, this will create cc* files, for example ccdjj2z9.o.271r.final
for -foffload=-fdump-rtl-final. (I don't know if you can come up with
dg-* directives to scan these.) The reason is -- I think -- because of
the lto-wrapper and/or mkoffloads not specifying a more suitable "base
name" for the temporary input files to lto1.
> That's not the problem. How to conditionally enable the test is the difficulty.
> I suspect porting something concerning accel_compiler from the libgomp
> testsuite is needed?
Use "{ target openacc_nvidia_accel_selected }", as implemented by
libgomp/testsuite/lib/libgomp.exp:check_effective_target_openacc_nvidia_accel_selected
(already present on trunk).
Grüße
Thomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
prev parent reply other threads:[~2015-11-11 17:16 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
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 [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=8737wcv4lg.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iverbin@gmail.com \
--cc=nathan@codesourcery.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).