From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: libgomp nvptx plugin: Debugging output for cuInit failure
Date: Tue, 23 May 2017 10:46:00 -0000 [thread overview]
Message-ID: <20170523104105.GP8499@tucnak> (raw)
In-Reply-To: <87efvhyrpn.fsf@hertz.schwinge.homeip.net>
On Mon, May 22, 2017 at 02:57:24PM +0200, Thomas Schwinge wrote:
> Hi!
>
> OK for trunk?
>
> commit 7b2f06b7d2fd23b20d81fda8be6ec7453e8b3fe3
> Author: Thomas Schwinge <thomas@codesourcery.com>
> Date: Thu Dec 22 08:30:04 2016 +0100
>
> libgomp nvptx plugin: Debugging output for cuInit failure
>
> libgomp/
> * plugin/plugin-nvptx.c (nvptx_get_num_devices): Debugging output
> for cuInit failure.
Ok.
Jakub
next prev parent reply other threads:[~2017-05-23 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 13:01 Thomas Schwinge
2017-05-23 10:46 ` Jakub Jelinek [this message]
2017-05-24 7:15 ` 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=20170523104105.GP8499@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@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).