From: Thomas Schwinge <thomas@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Cc: Julian Brown <julian@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
James Norris <jnorris@codesourcery.com>
Subject: [gomp4] Synchronous mode? (was: [1/3] OpenACC 2.0 support for libgomp - OpenACC runtime, NVidia PTX/CUDA plugin)
Date: Tue, 28 Oct 2014 19:42:00 -0000 [thread overview]
Message-ID: <874muogezu.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20141014171118.6cec6fb4@octopus>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
Hi!
One remark here, not related to the patch itself:
On Tue, 14 Oct 2014 17:11:18 +0100, Julian Brown <julian@codesourcery.com> wrote:
> --- /dev/null
> +++ b/libgomp/plugin-nvptx.c
> +//#define DISABLE_ASYNC
> +#ifndef DISABLE_ASYNC
> + [...]
> +#else
> + r = cuCtxSynchronize ();
> + if (r != CUDA_SUCCESS)
> + gomp_plugin_fatal ("cuCtxSynchronize error: %s", cuErrorMsg (r));
> +#endif
Earlier on, in discussion with Jim, we wondered whether it'd make sense
to expose the synchronous mode to the user (via an environment
variable?), which may help them when debugging? This is not a priority
right now, but perhaps something to keep in mind for later on.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2014-10-28 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 16:12 [gomp4] [1/3] OpenACC 2.0 support for libgomp - OpenACC runtime, NVidia PTX/CUDA plugin Julian Brown
2014-10-14 16:33 ` [gomp4] [2/3] OpenACC 2.0 support for libgomp - new tests Julian Brown
2014-10-14 16:12 ` [gomp] [3/3] OpenACC 2.0 support for libgomp - documentation Julian Brown
2014-10-16 17:06 ` [gomp4] [1/3] OpenACC 2.0 support for libgomp - OpenACC runtime, NVidia PTX/CUDA plugin Thomas Schwinge
2014-11-05 16:13 ` [gomp4] OpenACC documentation updates Thomas Schwinge
2014-10-28 16:07 ` [gomp4] [2/3] OpenACC 2.0 support for libgomp - new tests Thomas Schwinge
2014-10-29 19:54 ` [gomp4] libgomp: Also consider --with-cuda-driver flags for build-tree testing (was: [2/3] OpenACC 2.0 support for libgomp - new tests) Thomas Schwinge
2014-11-05 16:17 ` [gomp4] libgomp testsuite: OpenACC C++ " Thomas Schwinge
2014-11-13 13:32 ` [gomp4] [2/3] OpenACC 2.0 support for libgomp - new tests Thomas Schwinge
2014-10-28 16:15 ` [gomp4] [1/3] OpenACC 2.0 support for libgomp - OpenACC runtime, NVidia PTX/CUDA plugin Thomas Schwinge
2014-10-28 19:42 ` Thomas Schwinge [this message]
[not found] ` <541877C3.6080507@mentor.com>
2014-12-22 17:33 ` 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=874muogezu.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jnorris@codesourcery.com \
--cc=julian@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).