public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kwok Yeung <kcy@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-11] Fix goacc/noncontig_array-1.c testcase
Date: Thu, 13 May 2021 16:15:17 +0000 (GMT)	[thread overview]
Message-ID: <20210513161517.606B33AA7C87@sourceware.org> (raw)

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

commit dce9e5a0cbaa58b99c11fd1135f514dfdd6b096f
Author: Kwok Cheung Yeung <kcy@codesourcery.com>
Date:   Tue Jun 2 06:36:45 2020 -0700

    Fix goacc/noncontig_array-1.c testcase
    
    2020-06-02  Kwok Cheung Yeung  <kcy@codesourcery.com>
    
            gcc/testsuite/
            * c-c++-common/goacc/noncontig_array-1.c: Dump Gimple pass.

Diff:
---
 gcc/testsuite/ChangeLog.omp                          | 4 ++++
 gcc/testsuite/c-c++-common/goacc/noncontig_array-1.c | 1 +
 2 files changed, 5 insertions(+)

diff --git a/gcc/testsuite/ChangeLog.omp b/gcc/testsuite/ChangeLog.omp
index 9d8c7830ed9..a8a41238c4e 100644
--- a/gcc/testsuite/ChangeLog.omp
+++ b/gcc/testsuite/ChangeLog.omp
@@ -1,3 +1,7 @@
+2020-06-02  Kwok Cheung Yeung  <kcy@codesourcery.com>
+
+	* c-c++-common/goacc/noncontig_array-1.c: Dump Gimple pass.
+
 2020-03-27  Sandra Loosemore  <sandra@codesourcery.com>
 
 	* gfortran.dg/goacc/classify-kernels-unparallelized.f95: Adjust
diff --git a/gcc/testsuite/c-c++-common/goacc/noncontig_array-1.c b/gcc/testsuite/c-c++-common/goacc/noncontig_array-1.c
index ea738f5b65b..fe7480ab2e7 100644
--- a/gcc/testsuite/c-c++-common/goacc/noncontig_array-1.c
+++ b/gcc/testsuite/c-c++-common/goacc/noncontig_array-1.c
@@ -1,4 +1,5 @@
 /* { dg-do compile } */
+/* { dg-additional-options "-fdump-tree-gimple" } */
 
 void foo (void)
 {


                 reply	other threads:[~2021-05-13 16:15 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=20210513161517.606B33AA7C87@sourceware.org \
    --to=kcy@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).