From: Tobias Burnus <Tobias_Burnus@mentor.com>
To: Jakub Jelinek <jakub@redhat.com>,
Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch][Fortran/OpenMP] Don't create "alloc:" for 'target exit data'
Date: Wed, 30 Oct 2019 16:46:00 -0000 [thread overview]
Message-ID: <304773b3-802f-5b6f-0743-b75e9e231785@mentor.com> (raw)
In-Reply-To: <20191030155502.GZ4650@tucnak>
On 10/30/19 4:55 PM, Jakub Jelinek wrote:
> Do they? At least the C/C++ FEs should complain/remove before it makes
> its way into the middle-end. [â¦]
> Haven't checked the Fortran FE.
The Fortran FE lacks many checks the C/C++ FE has â but, admittedly, it
*does* have this check. (Which obviously does not apply to FE generated
code.)
> Ok.
Thanks for the quick review. (Committed as Rev. 277631.)
Tobias
next prev parent reply other threads:[~2019-10-30 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 10:13 Tobias Burnus
2019-10-24 7:29 ` *ping* " Tobias Burnus
2019-10-30 10:37 ` Jakub Jelinek
2019-10-30 15:50 ` Tobias Burnus
2019-10-30 15:58 ` Jakub Jelinek
2019-10-30 16:46 ` Tobias Burnus [this message]
2019-11-11 9:39 ` Thomas Schwinge
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=304773b3-802f-5b6f-0743-b75e9e231785@mentor.com \
--to=tobias_burnus@mentor.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).