public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc/devel/c++-coroutines] Merge master r11-7651. Date: Fri, 12 Mar 2021 21:35:24 +0000 (GMT) [thread overview] Message-ID: <20210312213524.355003857812@sourceware.org> (raw) https://gcc.gnu.org/g:9dd4b28d1a8068ef0e94d13f98bf77a521d8ca64 commit 9dd4b28d1a8068ef0e94d13f98bf77a521d8ca64 Merge: 4c4eb1f6c87 6e885ad3287 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Fri Mar 12 19:39:34 2021 +0000 Merge master r11-7651. * Merge master r11-7651-g6e885ad32873. Diff: ChangeLog | 9 + contrib/gcc-changelog/git_commit.py | 3 +- contrib/gcc-changelog/git_email.py | 2 +- contrib/gcc-changelog/setup.cfg | 3 + contrib/gcc-changelog/test_email.py | 4 + contrib/gcc-changelog/test_patches.txt | 30 ++ gcc/ChangeLog | 76 ++++ gcc/DATESTAMP | 2 +- gcc/Makefile.in | 4 +- gcc/analyzer/ChangeLog | 56 +++ gcc/analyzer/analyzer.opt | 8 + gcc/analyzer/diagnostic-manager.cc | 490 +++++++++++++++++++-- gcc/analyzer/diagnostic-manager.h | 6 +- gcc/analyzer/engine.cc | 99 +++-- gcc/analyzer/exploded-graph.h | 8 + gcc/analyzer/feasible-graph.cc | 235 ++++++++++ gcc/analyzer/feasible-graph.h | 213 +++++++++ gcc/analyzer/trimmed-graph.cc | 172 ++++++++ gcc/analyzer/trimmed-graph.h | 122 +++++ gcc/config/i386/constraints.md | 6 + gcc/config/i386/mmx.md | 179 ++++---- gcc/config/i386/sse.md | 292 ++++++------ gcc/config/rs6000/rs6000.c | 2 - gcc/config/rs6000/xcoff.h | 10 +- gcc/config/sparc/constraints.md | 9 +- gcc/config/sparc/sparc.c | 9 +- gcc/config/sparc/sparc.md | 12 +- gcc/config/sparc/sync.md | 6 +- gcc/cp/ChangeLog | 18 + gcc/cp/call.c | 4 + gcc/cp/module.cc | 5 + gcc/cp/name-lookup.c | 81 ++-- gcc/cp/ptree.c | 3 +- gcc/digraph.cc | 134 +++++- gcc/doc/analyzer.texi | 56 ++- gcc/doc/invoke.texi | 12 + gcc/fortran/resolve.c | 10 +- gcc/gimplify.c | 2 +- gcc/go/gofrontend/MERGE | 2 +- gcc/go/gofrontend/expressions.cc | 136 +++--- gcc/go/gofrontend/expressions.h | 5 + gcc/go/gofrontend/gogo.cc | 2 +- gcc/go/gofrontend/statements.cc | 6 +- gcc/go/gofrontend/wb.cc | 4 +- gcc/shortest-paths.h | 138 ++++-- gcc/testsuite/ChangeLog | 56 +++ gcc/testsuite/g++.dg/cpp2a/consteval19.C | 6 + gcc/testsuite/g++.dg/modules/pr99238.h | 1 + gcc/testsuite/g++.dg/modules/pr99238_a.H | 4 + gcc/testsuite/g++.dg/modules/pr99238_b.H | 8 + gcc/testsuite/g++.dg/modules/pr99248.h | 5 + gcc/testsuite/g++.dg/modules/pr99248_a.H | 5 + gcc/testsuite/g++.dg/modules/pr99248_b.H | 7 + gcc/testsuite/gcc.dg/analyzer/dot-output.c | 2 +- gcc/testsuite/gcc.dg/analyzer/feasibility-1.c | 16 +- .../analyzer/pr93355-localealias-feasibility-2.c | 4 +- .../analyzer/pr93355-localealias-feasibility-3.c | 8 +- .../analyzer/pr93355-localealias-feasibility.c | 2 - .../gcc.dg/analyzer/pr93355-localealias.c | 4 +- gcc/testsuite/gcc.dg/analyzer/unknown-fns-4.c | 2 +- gcc/testsuite/gcc.target/i386/avx512vl-pr99321-2.c | 94 ++++ gcc/testsuite/gfortran.dg/gomp/threadprivate-1.f90 | 11 + gcc/xcoffout.c | 1 - gcc/xcoffout.h | 1 - libgfortran/io/transfer.c | 32 +- libgfortran/io/unit.c | 1 - .../testsuite/libgomp.fortran/use_device_ptr-3.f90 | 91 ++++ libstdc++-v3/ChangeLog | 68 +++ libstdc++-v3/src/c++17/floating_to_chars.cc | 83 ++-- libstdc++-v3/src/c++17/ryu/LOCAL_PATCHES | 2 + libstdc++-v3/src/c++17/ryu/d2s_intrinsics.h | 4 - libstdc++-v3/src/c++17/ryu/generic_128.h | 3 - libstdc++-v3/src/c++17/ryu/ryu_generic_128.h | 4 +- libstdc++-v3/src/c++17/uint128_t.h | 297 +++++++++++++ .../testsuite/20_util/to_chars/long_double.cc | 1 - 75 files changed, 2914 insertions(+), 594 deletions(-)
reply other threads:[~2021-03-12 21:35 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=20210312213524.355003857812@sourceware.org \ --to=iains@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-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: linkBe 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).