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] (13 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Mon, 5 Sep 2022 08:18:59 +0000 (GMT) [thread overview]
Message-ID: <20220905081859.4F0263858D3C@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
d07ad71e727... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
479d1a062a5... amdgcn: OpenMP SIMD routine support
Diff:
Summary of changes (added commits):
-----------------------------------
d07ad71... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
8d2253f... nvptx: Silence unused variable warning in output_constant_p
92e848d... openmp: Partial OpenMP 5.2 doacross and omp_cur_iteration s
f4f72a2... Daily bump. (*)
29b456e... Daily bump. (*)
2d4f60f... rs6000: Don't ICE when we disassemble an MMA variable [PR10 (*)
a1caa42... Daily bump. (*)
3835765... cselib: add function to check if SET is redundant [PR106187 (*)
de1ba23... arm: correctly handle misaligned MEMs on MVE [PR105463] (*)
e69134e... AArch64: Fix bootstrap failure due to dump_printf_loc forma (*)
a114570... Daily bump. (*)
f959302... Fix up dump_printf_loc format attribute and adjust uses [PR (*)
b33602e... 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:[~2022-09-05 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 8:18 Tobias Burnus [this message]
2022-12-21 18:21 Tobias Burnus
2023-01-16 11:27 Tobias Burnus
2023-02-06 7:42 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=20220905081859.4F0263858D3C@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).