From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Cesar Philippidis <cesar@codesourcery.com>
Cc: thomas@codesourcery.com, fortran@gcc.gnu.org
Subject: Re: goacc/reduction-2.f95 failure
Date: Wed, 02 Dec 2015 21:44:00 -0000 [thread overview]
Message-ID: <20151202214435.GA12293@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20151202204924.GA88841@troutmask.apl.washington.edu>
On Wed, Dec 02, 2015 at 12:49:24PM -0800, Steve Kargl wrote:
> On Wed, Dec 02, 2015 at 12:42:40PM -0800, Cesar Philippidis wrote:
> > On 12/02/2015 12:33 PM, Steve Kargl wrote:
> >
> > > I just got a failure in the gfortran testsuite.
> > >
> > > FAIL: gfortran.dg/goacc/reduction-2.f95 -O scan-tree-dump-times \
> > > gimple "target oacc_kernels map.tofrom:a .len: 4.." 1
> > >
> > > Is this a known failure or expected?
> > >
> > > reduction-2.f95 was committed yesterday. Is something missing?
> >
> > How old is your build?
> >
> > I think Tom tweaked the default data mapping for kernels variables
> > yesterday either right before or after I committed a patch which
> > introduced that test case. That should be fixed in this patch
> >
> > https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00349.html
> >
> > which applied I applied to trunk about an hour ago.
> >
>
> It's about an hour old. I was testing the coarray events patch.
> In preparation for the commit, I updated the gcc/testsuite directory
> to get an up-to-date ChangeLog. I probably picked up a part of
> a commit. Rebuild from a top-of-tree as of 10 minutes ago. I know
> shortly if it is a false alarm.
Following up: it appears I had an inconsistent tree, so yes, a false alarm.
--
Steve
prev parent reply other threads:[~2015-12-02 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 20:33 Steve Kargl
2015-12-02 20:42 ` Cesar Philippidis
2015-12-02 20:49 ` Steve Kargl
2015-12-02 21:44 ` Steve Kargl [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=20151202214435.GA12293@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=cesar@codesourcery.com \
--cc=fortran@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).