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] (20 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Mon, 9 Jan 2023 09:21:29 +0000 (GMT) [thread overview]
Message-ID: <20230109092129.06BB73858C53@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
1624a774fad... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
9795d3d7ff6... OpenMP: GC unused SIMD clones
Diff:
Summary of changes (added commits):
-----------------------------------
1624a77... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
4494965... Daily bump. (*)
a68d0b4... Daily bump. (*)
6b1adeb... Daily bump. (*)
e824a27... Daily bump. (*)
ebb1f6d... libstdc++: Fix std::chrono::hh_mm_ss with unsigned rep [PR1 (*)
92ee4e1... rs6000: Raise error for __vector_{quad,pair} uses without M (*)
1359445... Daily bump. (*)
26741a0... c++: mark_single_function and SFINAE [PR108282] (*)
63f3eae... libiberty: Fix C89-isms in configure tests (*)
7d71461... libsanitizer: Avoid implicit function declaration in config (*)
b09c991... Daily bump. (*)
5618c81... Daily bump. (*)
2094b7a... Daily bump. (*)
9966231... Daily bump. (*)
f816ad1... Daily bump. (*)
b8102f4... Daily bump. (*)
4f1ece5... Daily bump. (*)
f97f032... Fortran: incorrect array bounds when bound intrinsic used i (*)
e5d19e3... Daily bump. (*)
(*) 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.
next reply other threads:[~2023-01-09 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 9:21 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-20 6:52 Tobias Burnus
2022-12-19 17:32 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=20230109092129.06BB73858C53@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).