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-10] (6 commits) Fortran: OpenMP - fix simd with (last)private (PR97061)
Date: Wed, 16 Sep 2020 14:50:52 +0000 (GMT) [thread overview]
Message-ID: <20200916145052.A6F55385EC4E@sourceware.org> (raw)
The branch 'devel/omp/gcc-10' was updated to point to:
e0e1d281472... Fortran: OpenMP - fix simd with (last)private (PR97061)
It previously pointed to:
15967a20162... Fix warning messages in libgomp.oacc-c++/privatized-ref-[23
Diff:
Summary of changes (added commits):
-----------------------------------
e0e1d28... Fortran: OpenMP - fix simd with (last)private (PR97061)
13ae89b... Merge remote-tracking branch 'origin/releases/gcc-10' into
5a7ae4f... [OpenMP] Fix mapping of artificial variables (PR94874)
3a6cb32... OpenMP/Fortran: Permit impure ELEMENTAL in omp directives
7e97e74... store-merging: Consider also overlapping stores earlier in (*)
97430fe... Daily bump. (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/omp/gcc-10' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2020-09-16 14:50 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=20200916145052.A6F55385EC4E@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).