public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-11] (16 commits) Merge branch 'releases/gcc-11' into devel/omp/gcc-11
Date: Sun, 23 May 2021 11:40:27 +0000 (GMT) [thread overview]
Message-ID: <20210523114027.8FBE33857C52@sourceware.org> (raw)
The branch 'devel/omp/gcc-11' was updated to point to:
4d83e2f9d03... Merge branch 'releases/gcc-11' into devel/omp/gcc-11
It previously pointed to:
a41b3c2af85... Fortran/OpenMP: Add support for 'close' in map clause
Diff:
Summary of changes (added commits):
-----------------------------------
4d83e2f... Merge branch 'releases/gcc-11' into devel/omp/gcc-11
040aef6... openmp: Fix up firstprivate+lastprivate clause handling [PR
dc9d8eb... openmp: Fix up handling of implicit lastprivate on outer co
9ee61d2... fortran/intrinsic.texi: Use proper variable name (*)
1d62f73... Daily bump. (*)
907a70b... Daily bump. (*)
2bf34b9... libsanitizer: Remove cyclades from libsanitizer (*)
3538242... Fix internal error on locally derived bit-packed array type (*)
36a70e6... Always translate Is_Pure flag into pure in C sense (*)
a9591c3... Fix segfault at run time on strict-alignment platforms (*)
5f78345... Fix incorrect SLOC on instruction (*)
cc7fc16... Daily bump. (*)
0a10104... c++: designated init with anonymous union [PR100489] (*)
e43f476... PR100281 C++: Fix SImode pointer handling (*)
a470d05... Fix gnat.dg spurious failures on PowerPC64 LE (*)
5f772bd... libstdc++: Disable floating_to_chars.cc on 16 bit targets (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/omp/gcc-11' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2021-05-23 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210523114027.8FBE33857C52@sourceware.org \
--to=burnus@gcc.gnu.org \
--cc=gcc-cvs@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).