public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/c++-coroutines] (17 commits) Merge master r12-6159.
Date: Fri, 31 Dec 2021 19:49:43 +0000 (GMT) [thread overview]
Message-ID: <20211231194943.6CFD33858D39@sourceware.org> (raw)
The branch 'devel/c++-coroutines' was updated to point to:
24d7992c8a3... Merge master r12-6159.
It previously pointed to:
abc5ef891cc... Merge master r12-6143.
Diff:
Summary of changes (added commits):
-----------------------------------
24d7992... Merge master r12-6159.
e3cbb8c... libgfortran: Fix bootstrap on targets without static_assert (*)
d9da496... testsuite: XFAIL some Wstringop-overflow tests ... (*)
84790a9... Daily bump. (*)
6c684aa... regrename: Fix -fcompare-debug issue in find_rename_reg [PR (*)
5545d1e... libcpp: Fix up ##__VA_OPT__ handling [PR89971] (*)
be674bd... libiberty: support digits in cpp mangled clone names (*)
52441f1... emit-rtl: Fix a -fcompare-debug issue due to var-tracking [ (*)
73898bc... docs: Add missing dash for argument. (*)
1dbe26b... c-family: Use BULTINS_LOCATION for predefined macros change (*)
1820137... shrink-wrapping: Fix up prologue block discovery [PR103860] (*)
dc1969d... loop-invariant: Don't move cold bb instructions to preheade (*)
be475aa... Daily bump. (*)
62c3f75... compiler, libgo: don't pad sparc64-linux epollevent (*)
e5acfca... tree-ssa-dce: Fix up -fcompare-debug failures in make_forwa (*)
ade9130... Fortran: keep values of IEEE_CLASS_TYPE in sync (*)
05edf6c... LTO: Prune some warnings in the testsuite (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/c++-coroutines' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2021-12-31 19:49 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=20211231194943.6CFD33858D39@sourceware.org \
--to=iains@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).