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] (12 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Fri, 9 Sep 2022 13:39:48 +0000 (GMT) [thread overview]
Message-ID: <20220909133948.7385D38582BF@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
0010ad7047c... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
de28004fa5f... amdgcn: Add support for additional natively supported float
Diff:
Summary of changes (added commits):
-----------------------------------
0010ad7... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
4ce316c... tree-optimization/106860 - fix profile scaling in split_loo (*)
41b4faa... tree-optimization/106841 - gather and hybrid SLP (*)
e08dd36... tree-optimization/106809 - compile time hog in VN (*)
98fed14... Daily bump. (*)
3a83d00... RTEMS: Add -mvrsave multilibs (*)
156607e... Daily bump. (*)
47f0bd2... libstdc++: Fix for explicit copy ctors in <thread> and <fut (*)
87da20c... libstdc++: Check for overflow in regex back-reference [PR10 (*)
6c08f8e... Daily bump. (*)
98fb37e... Daily bump. (*)
c1ba36e... Fortran: Fix ICE with -fcheck=pointer [PR100136] (*)
(*) 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-09 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 13:39 Tobias Burnus [this message]
2022-10-27 12:39 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=20220909133948.7385D38582BF@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).