public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/c++-modules] [testsuite, nvptx] Borrow ia64-sync-*.c test-cases in gcc.target/nvptx
Date: Thu, 27 Aug 2020 18:08:05 +0000 (GMT)	[thread overview]
Message-ID: <20200827180805.8FA3438708B7@sourceware.org> (raw)

https://gcc.gnu.org/g:a12026e9dd19caee8ce2f53e703564480e9709d4

commit a12026e9dd19caee8ce2f53e703564480e9709d4
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Aug 12 16:11:27 2020 +0200

    [testsuite, nvptx] Borrow ia64-sync-*.c test-cases in gcc.target/nvptx
    
    In absence of nvptx-enabling for effective target sync_int_long (see PR96494),
    copy a few test-cases to gcc.target/nvptx.
    
    Tested on nvptx.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/nvptx/ia64-sync-1.c: New test.
            * gcc.target/nvptx/ia64-sync-2.c: New test.
            * gcc.target/nvptx/ia64-sync-3.c: New test.
            * gcc.target/nvptx/ia64-sync-4.c: New test.

Diff:
---
 gcc/testsuite/gcc.target/nvptx/ia64-sync-1.c | 2 ++
 gcc/testsuite/gcc.target/nvptx/ia64-sync-2.c | 2 ++
 gcc/testsuite/gcc.target/nvptx/ia64-sync-3.c | 2 ++
 gcc/testsuite/gcc.target/nvptx/ia64-sync-4.c | 3 +++
 4 files changed, 9 insertions(+)

diff --git a/gcc/testsuite/gcc.target/nvptx/ia64-sync-1.c b/gcc/testsuite/gcc.target/nvptx/ia64-sync-1.c
new file mode 100644
index 00000000000..7685a799642
--- /dev/null
+++ b/gcc/testsuite/gcc.target/nvptx/ia64-sync-1.c
@@ -0,0 +1,2 @@
+/* { dg-do run } */
+#include "../../gcc.dg/ia64-sync-1.c"
diff --git a/gcc/testsuite/gcc.target/nvptx/ia64-sync-2.c b/gcc/testsuite/gcc.target/nvptx/ia64-sync-2.c
new file mode 100644
index 00000000000..d229b5f9181
--- /dev/null
+++ b/gcc/testsuite/gcc.target/nvptx/ia64-sync-2.c
@@ -0,0 +1,2 @@
+/* { dg-do run } */
+#include "../../gcc.dg/ia64-sync-2.c"
diff --git a/gcc/testsuite/gcc.target/nvptx/ia64-sync-3.c b/gcc/testsuite/gcc.target/nvptx/ia64-sync-3.c
new file mode 100644
index 00000000000..353fd74da57
--- /dev/null
+++ b/gcc/testsuite/gcc.target/nvptx/ia64-sync-3.c
@@ -0,0 +1,2 @@
+/* { dg-do run } */
+#include "../../gcc.dg/ia64-sync-3.c"
diff --git a/gcc/testsuite/gcc.target/nvptx/ia64-sync-4.c b/gcc/testsuite/gcc.target/nvptx/ia64-sync-4.c
new file mode 100644
index 00000000000..3547429fe09
--- /dev/null
+++ b/gcc/testsuite/gcc.target/nvptx/ia64-sync-4.c
@@ -0,0 +1,3 @@
+/* { dg-do compile } */
+/* { dg-options "-O2 -finline-functions" } */
+#include "../../gcc.dg/ia64-sync-4.c"


                 reply	other threads:[~2020-08-27 18:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200827180805.8FA3438708B7@sourceware.org \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-cvs@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).