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] (8 commits) Merge master r12-6143.
Date: Thu, 30 Dec 2021 00:10:35 +0000 (GMT) [thread overview]
Message-ID: <20211230001035.CE4263858400@sourceware.org> (raw)
The branch 'devel/c++-coroutines' was updated to point to:
abc5ef891cc... Merge master r12-6143.
It previously pointed to:
5380165c059... Merge master r12-6136.
Diff:
Summary of changes (added commits):
-----------------------------------
abc5ef8... Merge master r12-6143.
d8f6c48... Fortran: avoid several NULL pointer dereferences during err (*)
ad964f7... Support ld.mold linker. (*)
52a6b06... i386: Robustify some expanders w.r.t. paradoxical SUBREGs (*)
4437267... Fix ICE in lsplit when built with -O3 -fno-guess-branch-pro (*)
054e57e... Daily bump. (*)
0ac7bab... Libbacktrace: Fix the use of newline in sed replacement (*)
906b4e1... Fortran: Emit correct types for CHARACTER(C_CHAR), VALUE ar (*)
(*) 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-30 0:10 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=20211230001035.CE4263858400@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).