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] (14 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Thu, 1 Dec 2022 07:40:50 +0000 (GMT) [thread overview]
Message-ID: <20221201074050.B90C73858D37@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
e0233d8182c... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
02e6b3fd38d... libgomp.texi: List GCN's 'gfx803' under OpenMP Context Sele
Diff:
Summary of changes (added commits):
-----------------------------------
e0233d8... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
b7306f0... Fix unrecognizable insn due to illegal immediate_operand (c (*)
a802c4b... Daily bump. (*)
490b0c6... d: Include tm.h in all D target platform sources, remove me (*)
2909464... d: Fix ICE on named continue label in an unrolled loop [PR1 (*)
17d46f0... d: Fix #error You must define PREFERRED_DEBUGGING_TYPE if D (*)
6916332... Fix addvdi3 and subvdi3 patterns (*)
24b8b44... Daily bump. (*)
1fb5287... gcc: fix PR rtl-optimization/107482 (*)
9c1621e... Daily bump. (*)
131c10d... Daily bump. (*)
dbb468f... Daily bump. (*)
a1a7957... Daily bump. (*)
2a7a103... Fortran: reject NULL actual argument without explicit inter (*)
(*) 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:[~2022-12-01 7:40 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=20221201074050.B90C73858D37@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).