From: Nathan Sidwell <nathan@acm.org>
To: Thomas Schwinge <thomas@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gomp4] merge ptx changes
Date: Mon, 11 Jan 2016 14:16:00 -0000 [thread overview]
Message-ID: <5693B94D.1040406@acm.org> (raw)
In-Reply-To: <87r3ho5myb.fsf@kepler.schwinge.homeip.net>
On 01/11/16 07:18, Thomas Schwinge wrote:
> Hi!
>
> On Tue, 5 Jan 2016 09:22:46 -0500, Nathan Sidwell <nathan@acm.org> wrote:
>> This patch merges my most recent sequence of ptx backend changes to the gomp4
>> branch.
>
> I suppose it's not been intentional that during that, you dropped some of
> the changes present on gomp-4_0-branch, once installed for "[gomp4] Basic
> -misa support for nvptx",
> <http://news.gmane.org/find-root.php?message_id=%3C87lhgsjhf9.fsf%40schwinge.name%3E>?
> In gomp-4_0-branch r232224, I restored that code (untested) as follows:
thanks. I thought I'd preserved all the bits, but clearly missed those.
nathan
prev parent reply other threads:[~2016-01-11 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 14:22 Nathan Sidwell
2016-01-11 12:18 ` Thomas Schwinge
2016-01-11 14:16 ` Nathan Sidwell [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=5693B94D.1040406@acm.org \
--to=nathan@acm.org \
--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).