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] (16 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Mon, 12 Dec 2022 14:26:10 +0000 (GMT) [thread overview]
Message-ID: <20221212142610.C712E385B51E@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
daf3af9e5b6... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
f9ea81c07e9... libgomp: Handle OpenMP's reverse offloads
Diff:
Summary of changes (added commits):
-----------------------------------
daf3af9... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
1a8af01... tree-optimization/107898 - ICE with -Walloca-larger-than (*)
0946970... tree-optimization/107865 - ICE with outlining of loops (*)
812847a... tree-optimization/107833 - invariant motion of uninit uses (*)
232305b... tree-optimization/107686 - fix bitfield ref through vec_unp (*)
9e242f8... tree-optimization/107766 - ICE with recent -ffp-contract=of (*)
a9fafa2... tree-optimization/107647 - avoid FMA from SLP with -ffp-con (*)
e0e37f9... tree-optimization/107407 - wrong code with DSE (*)
ad6ace7... tree-optimization/106868 - bogus -Wdangling-pointer diagnos (*)
86def97... Daily bump. (*)
db8e343... d: Remove "final" and "override" from visitor method. (*)
f12c822... d: Fix internal compiler error: in visit, at d/imports.cc:7 (*)
42156d7... Daily bump. (*)
3ee5a23... Daily bump. (*)
5ec102e... i386: fix assert (__builtin_cpu_supports ("x86-64") >= 0) (*)
b4e5003... i386: simplify cpu_feature handling (*)
(*) 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-12 14:26 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=20221212142610.C712E385B51E@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).