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] (38 commits) Merge master r12-7249.
Date: Tue, 15 Feb 2022 23:39:05 +0000 (GMT) [thread overview]
Message-ID: <20220215233905.98C9A385800F@sourceware.org> (raw)
The branch 'devel/c++-coroutines' was updated to point to:
8488c61a324... Merge master r12-7249.
It previously pointed to:
da059215a35... Merge master r12-7212.
Diff:
Summary of changes (added commits):
-----------------------------------
8488c61... Merge master r12-7249.
8e84b2b... aarch64: Fix subs_compare_2.c regression [PR100874] (*)
65df3ae... aarch64: Fix store_v2vec_lanes.c failure (*)
fd77b12... aarch64: Add +nosve to tests (*)
4963079... vect+aarch64: Fix ldp_stp_* regressions (*)
63a9328... vect: Fix early free (*)
6cfb7ff... libstdc++: Add missing constexpr to uses-allocator construc (*)
d03a67d... tree-optimization/104543 - fix unroll-and-jam precondition (*)
3939c1b... Fortran/OpenMP: Fix depend-clause handling (*)
0863d0e... cygwin: Fix up -Werror=format-diag errors [PR104536] (*)
2801f23... fold, simplify-rtx: Punt on non-representable floating poin (*)
d8b6da8... tree-optimization/104519 - adjust PR100499 niter fix (*)
c4c0aa6... sanitizer: Use glibc _thread_db_sizeof_pthread symbol if pr (*)
6a0d6e7... openmp: Make finalize_task_copyfn order reproduceable [PR10 (*)
2c3309e... c++: TTP in member alias template [PR104107] (*)
1f8a09d... Daily bump. (*)
7a1b179... Update -Warray-bounds documentation [PR104355]. (*)
16b65b0... Use correct names for __ibm128 if long double is IEEE 128-b (*)
19b517d... Fortran: improve error recovery on bad array section (*)
3d50ded... libstdc++: Fix stream extraction of IEEE128 long double [PR (*)
02a981a... c++: Don't reject GOTO_EXPRs to cdtor_label in potential_co (*)
d51cad0... amdgcn: Allow vector reductions on constants (*)
0a1a3af... tree-optimization/104528 - free niter estimates after DSE (*)
164a761... libstdc++: Use __cpp_concepts instead of custom macro [PR10 (*)
220d85f... libstdc++: Fix typo in pragma (*)
8134156... libstdc++: Fix std::to_chars for IEEE128 long double (*)
f320197... tree-optimization/104511 - avoid FP to DFP conversion for V (*)
f7e2691... c/104505 - ICE with internal function call in diagnostic ex (*)
3f10e0d... middle-end/104497 - gimplification of vector indexing (*)
0d31c8e... Daily bump. (*)
4493c5a... [Ada] PR ada/98724: Alpha/Linux/libada: Use wraplf for Aux_ (*)
58aeb75... runtime: call timer functions via syscall (*)
033ec96... compiler: don't set ptrmask bit for pointer to notinheap ty (*)
57da349... fortran: Unshare associate var charlen [PR104228] (*)
7e204bd... Add vect_recog_cond_expr_convert_pattern. (*)
23756b7... Daily bump. (*)
f0c7367... asan: Fix up address sanitizer instrumentation of __builtin (*)
5c4258d... x86: Update PR 35513 tests (*)
(*) 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:[~2022-02-15 23:39 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=20220215233905.98C9A385800F@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).