From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch][v2] OpenMP/Fortran: Partially fix non-rect loop nests [PR107424]
Date: Thu, 9 Feb 2023 15:49:46 +0100 [thread overview]
Message-ID: <Y+UICuVT63TvTyiK@tucnak> (raw)
In-Reply-To: <b82423ad-147c-b083-7d21-e23ea3c0928b@codesourcery.com>
On Thu, Feb 09, 2023 at 03:46:35PM +0100, Tobias Burnus wrote:
> I think the test coverage should be sufficient. Any further test idea?
> Otherwise, I would commit it now.
LGTM, thanks.
Jakub
prev parent reply other threads:[~2023-02-09 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 14:40 [Patch] " Tobias Burnus
2023-01-20 17:39 ` Jakub Jelinek
2023-01-20 18:00 ` Jakub Jelinek
2023-01-20 20:02 ` Jakub Jelinek
2023-01-25 14:47 ` [Patch][v2] " Tobias Burnus
2023-01-31 11:37 ` Jakub Jelinek
2023-02-09 14:46 ` Tobias Burnus
2023-02-09 14:49 ` Jakub Jelinek [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=Y+UICuVT63TvTyiK@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@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).