From: Sandra Loosemore <sandra.loosemore@siemens.com>
To: Jakub Jelinek <jakub@redhat.com>,
Sandra Loosemore <sandra@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH V2 2/5] OpenMP: C front end support for imperfectly-nested loops
Date: Tue, 22 Aug 2023 12:53:19 -0600 [thread overview]
Message-ID: <933fb549-d9c7-bd9a-38a3-ebaea075d6ee@siemens.com> (raw)
In-Reply-To: <ZOS23tuDLb9VEOpa@tucnak>
On 8/22/23 07:23, Jakub Jelinek wrote:
>
>> diff --git a/gcc/testsuite/c-c++-common/goacc/collapse-1.c b/gcc/testsuite/c-c++-common/goacc/collapse-1.c
>> index 11b14383983..0feac8f8ddb 100644
>> --- a/gcc/testsuite/c-c++-common/goacc/collapse-1.c
>> +++ b/gcc/testsuite/c-c++-common/goacc/collapse-1.c
>> @@ -8,8 +8,8 @@ f1 (void)
>> {
>> #pragma acc parallel
>> #pragma acc loop collapse (2)
>> - for (i = 0; i < 5; i++)
>> - ; /* { dg-error "not enough perfectly nested" } */
>> + for (i = 0; i < 5; i++) /* { dg-error "not enough nested loops" } */
>> + ;
>> {
>> for (j = 0; j < 5; j++)
>> ;
>
> All these c-c++-common testsuite changes will now FAIL after the C patch but
> before the C++. It is nice to have the new c-c++-common tests in a separate
> patch, but these tweaks which can't be just avoided need the temporary
> { target c } vs. { target c++} hacks undone later in the C++ patch.
In spite of being in the c-c++-common subdirectory, this particular testcase is
presently run only for C:
/* { dg-skip-if "not yet" { c++ } } */
I did previously do incremental testing between applying the the C and C++
parts of the series to confirm that there were no regressions.
BTW, thanks for your previous detailed review of the original version of this
patch, and pointing out many things I'd overlooked; I feel that V2 is much more
robust and correct as a result. :-)
-Sandra
next prev parent reply other threads:[~2023-08-22 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 22:15 [PATCH V2 0/5] OpenMP: " Sandra Loosemore
2023-07-23 22:15 ` [PATCH V2 1/5] OpenMP: Add OMP_STRUCTURED_BLOCK and GIMPLE_OMP_STRUCTURED_BLOCK Sandra Loosemore
2023-08-22 13:01 ` Jakub Jelinek
2023-07-23 22:15 ` [PATCH V2 2/5] OpenMP: C front end support for imperfectly-nested loops Sandra Loosemore
2023-08-22 13:23 ` Jakub Jelinek
2023-08-22 18:53 ` Sandra Loosemore [this message]
2023-08-24 11:49 ` Jakub Jelinek
2023-07-23 22:15 ` [PATCH V2 3/5] OpenMP: C++ " Sandra Loosemore
2023-08-22 13:31 ` Jakub Jelinek
2023-07-23 22:15 ` [PATCH V2 4/5] OpenMP: New C/C++ testcases for imperfectly nested loops Sandra Loosemore
2023-08-22 13:34 ` Jakub Jelinek
2023-07-23 22:15 ` [PATCH V2 5/5] OpenMP: Fortran support for imperfectly-nested loops Sandra Loosemore
2023-08-22 13:37 ` Jakub Jelinek
2023-08-24 16:36 ` Tobias Burnus
2023-08-22 12:56 ` [PATCH V2 0/5] OpenMP: " Jakub Jelinek
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=933fb549-d9c7-bd9a-38a3-ebaea075d6ee@siemens.com \
--to=sandra.loosemore@siemens.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=sandra@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).