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: Thu, 27 Oct 2022 12:39:42 +0000 (GMT) [thread overview]
Message-ID: <20221027123942.416DC3853541@sourceware.org> (raw)
The branch 'devel/omp/gcc-12' was updated to point to:
ceab31ff040... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
It previously pointed to:
9c461798d5d... Handle operator new with alignment in usm transform.
Diff:
Summary of changes (added commits):
-----------------------------------
ceab31f... Merge branch 'releases/gcc-12' into devel/omp/gcc-12
ca0220d... lto: do not load LTO stream for aliases [PR107418] (*)
72717ec... IRA: Make sure array is big enough (*)
e089e35... Daily bump. (*)
3668a59... aarch64: update Ampere-1 core definition (*)
4b54eb8... aarch64: fix off-by-one in reading cpuinfo (*)
29a1eb4... Daily bump. (*)
da1f6e5... Relax assertion in profiler (*)
0737125... IBM zSystems: Fix function_ok_for_sibcall [PR106355] (*)
2a2093a... i386: fix pedantic warning (*)
4db0753... x86: fix VENDOR_MAX enum value (*)
cd29fc9... 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-10-27 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 12:39 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-09 13: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=20221027123942.416DC3853541@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).