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] (14 commits) Merge remote-tracking branch 'origin/releases/gcc-11' into
Date: Tue, 2 Nov 2021 15:01:53 +0000 (GMT) [thread overview]
Message-ID: <20211102150153.414E83858D35@sourceware.org> (raw)
The branch 'devel/omp/gcc-11' was updated to point to:
98e6a28f9a8... Merge remote-tracking branch 'origin/releases/gcc-11' into
It previously pointed to:
f76fc6740a9... Merge remote-tracking branch 'origin/releases/gcc-11' into
Diff:
Summary of changes (added commits):
-----------------------------------
98e6a28... Merge remote-tracking branch 'origin/releases/gcc-11' into
798ebb8... openmp: Add testcase for threadprivate random access class
2b4bd2b... openmp: Diagnose threadprivate OpenMP loop iterators
fdc2700... Daily bump. (*)
0111975... libstdc++: Fix range access for empty std::valarray [PR1030 (*)
d0d8bd6... Daily bump. (*)
cfc3c75... Daily bump. (*)
ee13a30... Daily bump. (*)
818961c... Daily bump. (*)
4719d05... Update documentation of %X spec (*)
3e2ccaa... Daily bump. (*)
5782bac... Fortran: do not restrict PDT KIND and LEN type parameters t (*)
70c3fa5... Fix warnings building linux-atomic.c and fptr.c on hppa64-l (*)
97cebda... sra: Fix corner case of total scalarization with virtual in (*)
(*) 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.
next reply other threads:[~2021-11-02 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:01 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-06 13:31 Tobias Burnus
2021-06-08 8:15 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=20211102150153.414E83858D35@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).