From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [OG11] Merge GCC 11 into branch, cherry picks from mainline
Date: Wed, 21 Jul 2021 10:38:57 +0200 [thread overview]
Message-ID: <3e815b08-edd3-3550-58d2-a239a9ce2355@codesourcery.com> (raw)
In-Reply-To: <3846fd61-4bb9-b027-fc87-774a2848eac9@codesourcery.com>
OG11 = devel/omp/gcc-11, a branch with some OpenMP/OpenACC/offload patches
which are not yet on mainline. Additionally, patches in this area are
cherry-picked from mainline.
Commits since my last email on 15 June 21 which ended with commit adda89fd071.
My commits are all only cherry-picks plus GCC11 merges and some fallout
commits. Thus, a rather boring list and nothing sophisticate.
But for completeness, those commits are hereby documented.
[I am not quite sure who actually is interested in this list.]
The list includes all commits in this span, including those
by others.
Cherry pick from mainline by me:
2021-06-15 35b3fbf5d52 Fortran/OpenMP: Extend defaultmap clause for OpenMP 5 [PR92568]
Interlude: ChungLin's commit (no cherry pick):
2021-06-17 dbf5d72f4c0 Fixes for lambda in offload regions
Cherry picks by Marcel (first one), Andrew (amdgcn one) and me (rest)
from mainline – plus git merge from the GCC 11 branch:
2021-06-22 9cb373f4439 gcc/configure.ac: fix register issue for global_load assembler functions
2021-06-23 235d6eda48d openmp: Fix up *_reduction clause handling with UDRs on PARM_DECLs [PR101167]
2021-06-23 7cadfa1e4c8 Merge remote-tracking branch 'origin/releases/gcc-11' into devel/omp/gcc-11
2021-06-28 4c7c00c362e fortran/dump-parse-tree.c: Use proper enum type
2021-06-28 a82a305d19c Merge remote-tracking branch 'origin/releases/gcc-11' into devel/omp/gcc-11
2021-06-29 5536f1065fe libgomp.fortran/defaultmap-8.f90: Fix non-shared memory handling
2021-06-29 33ef3d64e4d doc/invoke.texi: Sort flags in 'C Language Options'
2021-06-29 1e42bad6b96 Add 'default' to -foffload=; document that flag [PR67300]
2021-06-29 6f08285014b gcc.c: Silence warning in check_offload_target_name
2021-07-19 e054a4f7784 gcc/ChangeLog.omp: Update for last commit
2021-07-19 e897bb0c27d openmp: Reject #pragma omp atomic update, [PR101297]
2021-07-19 36de16fd74f openmp: Initial support for OpenMP directives expressed as C++11 attributes
2021-07-20 f2f97e59bd2 Merge remote-tracking branch 'origin/releases/gcc-11' into devel/omp/gcc-11
2021-07-20 d47128d328f amdgcn: Add -mxnack and -msram-ecc [PR 100208]
2021-07-21 1201a27fba3 Fortran: Fix bind(C) character length checks
2021-07-21 a0b34d73e34 c++: Ensure OpenMP reduction with reference type references complete type [PR101516]
2021-07-21 858d20e2945 openmp: Fix up omp_check_private [PR101535]
Cheers,
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
next prev parent reply other threads:[~2021-07-21 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 8:51 Tobias Burnus
2021-05-17 10:33 ` Tobias Burnus
2021-05-23 11:45 ` Tobias Burnus
2021-06-15 10:28 ` Tobias Burnus
2021-07-21 8:38 ` Tobias Burnus [this message]
2021-07-27 10:02 ` Tobias Burnus
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=3e815b08-edd3-3550-58d2-a239a9ce2355@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@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).