public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [gomp] Move openacc vector& worker single handling to RTL
Date: Mon, 20 Jul 2015 13:19:00 -0000	[thread overview]
Message-ID: <55ACF144.4050201@acm.org> (raw)
In-Reply-To: <87bnf9v5ma.fsf@kepler.schwinge.homeip.net>

On 07/18/15 11:37, Thomas Schwinge wrote:
> Hi Nathan!

> For OpenACC nvptx offloading, there must still be something wrong; here's
> a count of the (non-deterministic!) regressions of ten runs of the
> libgomp testsuite.  As private-vars-loop-worker-5.c fails most often, it
> probably makes sense to look into that one first.

I'll take a look. :(

nathan

  reply	other threads:[~2015-07-20 13:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 22:52 Nathan Sidwell
2015-07-03 23:12 ` Jakub Jelinek
2015-07-04 20:41   ` Nathan Sidwell
2015-07-06 19:35     ` Nathan Sidwell
2015-07-07  9:54       ` Jakub Jelinek
2015-07-07 14:13         ` Nathan Sidwell
2015-07-07 14:22           ` Jakub Jelinek
2015-07-07 14:43             ` Nathan Sidwell
2015-07-08 14:48             ` Nathan Sidwell
2015-07-08 14:58               ` Jakub Jelinek
2015-07-08 21:46                 ` Nathan Sidwell
2015-07-10  0:25                   ` Nathan Sidwell
2015-07-10  9:04                     ` Thomas Schwinge
2015-07-11 19:25                       ` [gomp4] Revert "Work around nvptx offloading compiler --enable-checking=yes,df,fold,rtl breakage" (was: fix df verify failure) Thomas Schwinge
2015-07-13 11:26                       ` [gomp] Move openacc vector& worker single handling to RTL Thomas Schwinge
2015-07-13 13:23                         ` Nathan Sidwell
     [not found]                         ` <55A7D5DD.2070600@mentor.com>
2015-07-17  9:00                           ` [gomp] Fix PTX worker spill/fill Thomas Schwinge
2015-07-11 21:18                     ` [gomp4] Resolve bootstrap failure in expand_GOACC_FORK, expand_GOACC_JOIN (was: Move openacc vector& worker single handling to RTL) Thomas Schwinge
2015-07-14  8:26                     ` [gomp] Move openacc vector& worker single handling to RTL Thomas Schwinge
2015-07-15  2:41                       ` Nathan Sidwell
2015-07-18 20:31                     ` Thomas Schwinge
2015-07-20 13:19                       ` Nathan Sidwell [this message]
2015-07-20 15:56                         ` Nathan Sidwell
2015-07-22 17:05                           ` Nathan Sidwell
2015-07-23  8:52                             ` [gomp4] libgomp: Some torture testing for C and C++ OpenACC test cases (was: [gomp] Move openacc vector& worker single handling to RTL) Thomas Schwinge
2015-07-21 20:57                       ` [gomp] Move openacc vector& worker single handling to RTL Nathan Sidwell
2015-07-22  8:32                         ` Thomas Schwinge
2015-12-01  9:07                     ` Thomas Schwinge
2015-07-10 22:04 [gomp] fix df verify failure Nathan Sidwell
2015-07-16 17:18 [gomp] Fix PTX worker spill/fill Nathan Sidwell
     [not found] ` <55A7D4BA.2000309@mentor.com>
2015-07-17  9:29   ` 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=55ACF144.4050201@acm.org \
    --to=nathan@acm.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).