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] (18 commits) Merge master r12-3984.
Date: Thu, 30 Sep 2021 19:55:16 +0000 (GMT) [thread overview]
Message-ID: <20210930195516.215693858C2C@sourceware.org> (raw)
The branch 'devel/c++-coroutines' was updated to point to:
8ee438cd62b... Merge master r12-3984.
It previously pointed to:
d8c56bfff60... Merge master r12-3967.
Diff:
Summary of changes (added commits):
-----------------------------------
8ee438c... Merge master r12-3984.
ef37ddf... libgomp.fortran/alloc-*.f90: Add missing dg-prune-output (*)
70de20d... openmp: Add omp_aligned_{,c}alloc and omp_{c,re}alloc for F (*)
c3d11a1... testsuite: Skip a test-case when LTO is used [PR102509] (*)
32bd81e... Do not hide asm_out_file in ASM_OUTPUT_ASCII. (*)
09f032c... Refine alingment peeling fix (*)
c2dc29c... Fix thinko in previous alignment peeling change (*)
c536996... libstdc++: Fix preprocessor check for C++17 (*)
f5440ac... Plug possible snprintf overflow in lto-wrapper. (*)
b38a4bd... openmp: Add omp_aligned_{,c}alloc and omp_{c,re}alloc (*)
257fd03... Add gimple_ranger::debug. (*)
64dd46d... Plug memory leak in hybrid_threader. (*)
d238146... Daily bump. (*)
d6a87d9... debug/102507: ICE in btf_finalize when compiling with -gbtf (*)
cd5448f... MAINTAINERS: Add myself to DCO section (*)
24e30f4... [PR102501] Adjust jump threading testcases for ppc64* and o (*)
77731cb... Avoid CFG updates in VRP threader if nothing changed. (*)
48c97c6... Use a separate TV_* timer for the VRP threader. (*)
(*) 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-09-30 19:55 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=20210930195516.215693858C2C@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).