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-12] (8 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Thu, 19 Jan 2023 20:23:55 +0000 (GMT) [thread overview]
Message-ID: <20230119202355.68D683858C53@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
8787039dbe0... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
495b7c3a3f7... libgomp: Add forgotten Changelog.omp entries
Diff:
Summary of changes (added commits):
-----------------------------------
8787039... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
1184c55... openmp: Fix up OpenMP expansion of non-rectangular loops [P
61ef24a... Daily bump. (*)
937b0f0... libstdc++: Avoid recursion in __nothrow_wait_cv::wait [PR10 (*)
e80bb40... Daily bump. (*)
e95fa8c... Daily bump. (*)
24a6848... Add cpplib ka.po (*)
1dfe15e... libstdc++: Unblock atomic wait on non-futex platforms [PR10 (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/omp/gcc-12' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2023-01-19 20:23 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=20230119202355.68D683858C53@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).