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, 8 Jun 2021 08:15:35 +0000 (GMT) [thread overview]
Message-ID: <20210608081535.E56B8384781B@sourceware.org> (raw)
The branch 'devel/omp/gcc-11' was updated to point to:
1bd8a177994... Merge remote-tracking branch 'origin/releases/gcc-11' into
It previously pointed to:
e3433dd498e... openmp: Add testcase for scan directive with nested functio
Diff:
Summary of changes (added commits):
-----------------------------------
1bd8a17... Merge remote-tracking branch 'origin/releases/gcc-11' into
1ab881d... Fortran/OpenMP: Fix clause splitting for target/parallel/te
f3c9f93... Daily bump. (*)
e62029a... c++: using-enum and access specifiers [PR100862] (*)
f1feb74... c++: tsubst_function_decl and excess arg levels [PR100102] (*)
23fa1e7... libstdc++: add missing typename for dependent type in range (*)
bcb5e97... x86: Update g++.target/i386/pr100885.C (*)
c064e78... Fix ICE of insn does not satisfy its constraints. (*)
505fb23... Daily bump. (*)
002745c... PR fortran/98301 - random_init() is broken (*)
4fff5f1... Daily bump. (*)
d04fca1... Daily bump. (*)
83f932f... d: Fix ICE in gimplify_var_or_parm_decl, at gimplify.c:2755 (*)
2fdca7c... Fortran - ICE in inline_matmul_assign (*)
(*) 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-06-08 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 8:15 Tobias Burnus [this message]
2021-09-06 13:31 Tobias Burnus
2021-11-02 15:01 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=20210608081535.E56B8384781B@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).