From: Tobias Burnus <tobias@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Patch ping related to OpenMP
Date: Mon, 20 Dec 2021 12:47:55 +0100 [thread overview]
Message-ID: <46b4ffe2-f125-2c96-c8d9-2d187c49033b@codesourcery.com> (raw)
In-Reply-To: <83a9f1b0-eec8-d01f-99d1-d1b8ee5ad301@codesourcery.com>
Thanks for a DWARF-related patch review (+ fix by yourself). Otherwise,
still pending are the following OpenMP patches.
The first one is a revised patch following the review comment and
affects Fortran only. The second one is also a rather small &
post-review revised patch.
On 06.12.21 15:56, Tobias Burnus wrote:
> First, thanks for the four reviews. Secondly, I missed one patch –
> hence, reposted with all three pending patches:
>
> * Re: [PATCH] [gfortran] Add support for allocate clause (OpenMP 5.0).
> https://gcc.gnu.org/pipermail/gcc-patches/2021-November/584894.html
>
> and:
>
> On 01.12.21 17:34, Tobias Burnus wrote:
>> * [PATCH] C, C++, Fortran, OpenMP: Add 'has_device_addr' clause to
>> 'target' construct
>> https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585361.html
>>
>> * [PATCH 00/16] OpenMP: lvalues in "map" clauses and struct handling
>> rework
>> https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585439.html
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2021-12-20 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 16:34 Tobias Burnus
2021-12-06 14:56 ` Tobias Burnus
2021-12-20 11:47 ` Tobias Burnus [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=46b4ffe2-f125-2c96-c8d9-2d187c49033b@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).