public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66332] goacc/acc_on_device-2.c scan-rtl-dump-times expand testsuite failure
Date: Tue, 02 Jun 2015 11:49:00 -0000	[thread overview]
Message-ID: <bug-66332-4-o93b38Cv4P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66332-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66332

--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Tue Jun  2 11:48:56 2015
New Revision: 224028

URL: https://gcc.gnu.org/viewcvs?rev=224028&root=gcc&view=rev
Log:
[PR libgomp/65742, PR middle-end/66332] XFAIL acc_on_device compile-time
evaluation

The OpenACC 2.0a specification mandates differently, but we currently do get a
library call in the host code.

        PR libgomp/65742
        PR middle-end/66332

        gcc/testsuite/
        * c-c++-common/goacc/acc_on_device-2.c: XFAIL for C, too.

Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/c-c++-common/goacc/acc_on_device-2.c


  parent reply	other threads:[~2015-06-02 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  1:46 [Bug go/66332] New: " jpsinthemix at verizon dot net
2015-05-29  5:41 ` [Bug middle-end/66332] " tschwinge at gcc dot gnu.org
2015-06-02 11:49 ` tschwinge at gcc dot gnu.org [this message]
2015-06-02 12:05 ` tschwinge at gcc dot gnu.org
2015-07-15 11:55 ` tschwinge at gcc dot gnu.org
2015-07-31 14:14 ` tschwinge at gcc dot gnu.org
2015-08-10 16:49 ` tschwinge at gcc dot gnu.org
2015-09-10 15:58 ` sje at gcc dot gnu.org

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=bug-66332-4-o93b38Cv4P@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).