public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] Merge branch 'master' into devel/sphinx
Date: Thu, 19 Aug 2021 10:03:40 +0000 (GMT) [thread overview]
Message-ID: <20210819100340.9DE85382CC36@sourceware.org> (raw)
https://gcc.gnu.org/g:0b6c24dd10ff426108f737551067085d0af42ca8
commit 0b6c24dd10ff426108f737551067085d0af42ca8
Merge: 60ae041aae4 301dc6011cb
Author: Martin Liska <mliska@suse.cz>
Date: Thu Aug 19 12:03:21 2021 +0200
Merge branch 'master' into devel/sphinx
Diff:
ChangeLog | 6 +
Makefile.in | 3 +
Makefile.tpl | 3 +
config/ChangeLog | 5 +
config/mh-darwin | 8 +
contrib/ChangeLog | 6 +
gcc/ChangeLog | 51 ++++
gcc/DATESTAMP | 2 +-
gcc/ada/ChangeLog | 5 +
gcc/analyzer/ChangeLog | 51 ++++
gcc/analyzer/analysis-plan.cc | 4 +
gcc/analyzer/checker-path.cc | 28 +-
gcc/analyzer/checker-path.h | 6 +
gcc/analyzer/diagnostic-manager.cc | 23 +-
gcc/analyzer/engine.cc | 183 +++++++++++
gcc/analyzer/exploded-graph.h | 39 +++
gcc/analyzer/program-point.cc | 18 ++
gcc/analyzer/program-point.h | 3 +-
gcc/analyzer/program-state.cc | 44 +++
gcc/analyzer/program-state.h | 11 +
gcc/analyzer/region-model.cc | 49 ++-
gcc/analyzer/region-model.h | 6 +
gcc/analyzer/state-purge.cc | 35 ++-
gcc/analyzer/supergraph.cc | 43 ++-
gcc/analyzer/supergraph.h | 7 +-
gcc/c-family/ChangeLog | 6 +
gcc/c/ChangeLog | 29 ++
gcc/c/c-parser.c | 15 +-
gcc/config.gcc | 2 +-
gcc/config/aarch64/arm_neon.h | 8 +-
gcc/config/darwin.h | 3 +-
gcc/config/i386/i386.c | 6 +-
gcc/config/i386/i386.h | 1 -
gcc/config/i386/x86-tune-costs.h | 26 --
gcc/cp/ChangeLog | 39 +++
gcc/cp/parser.c | 17 +-
gcc/fortran/ChangeLog | 6 +
gcc/hash-map-tests.c | 17 +-
gcc/jit/ChangeLog | 5 +
gcc/jit/Make-lang.in | 63 +++-
gcc/jit/docs/examples/tut04-toyvm/toyvm.c | 2 +-
gcc/jit/docs/examples/tut04-toyvm/toyvm.cc | 2 +-
gcc/jit/jit-dejagnu.h | 338 +++++++++++++++++++++
gcc/objc/ChangeLog | 10 +
gcc/objc/objc-act.c | 16 +-
gcc/objc/objc-next-runtime-abi-02.c | 22 +-
gcc/optabs.c | 79 +++++
gcc/testsuite/ChangeLog | 74 +++++
gcc/testsuite/c-c++-common/gomp/nothing-2.c | 2 +
gcc/testsuite/c-c++-common/gomp/requires-3.c | 2 +
gcc/testsuite/g++.dg/analyzer/vfunc-2.C | 44 +++
gcc/testsuite/g++.dg/analyzer/vfunc-3.C | 32 ++
gcc/testsuite/g++.dg/analyzer/vfunc-4.C | 28 ++
gcc/testsuite/g++.dg/analyzer/vfunc-5.C | 103 +++++++
gcc/testsuite/gcc.dg/analyzer/function-ptr-4.c | 24 ++
gcc/testsuite/gcc.dg/analyzer/pr100546.c | 17 ++
gcc/testsuite/gcc.dg/pr78213.c | 3 +-
gcc/testsuite/gcc.target/i386/pr101950-1.c | 20 ++
gcc/testsuite/gcc.target/i386/pr101950-2.c | 19 ++
gcc/testsuite/gcc.target/i386/pr99881.c | 2 +-
gcc/testsuite/gfortran.dg/{ => gomp}/nothing-1.f90 | 0
gcc/testsuite/gfortran.dg/{ => gomp}/nothing-2.f90 | 2 +-
gcc/testsuite/jit.dg/harness.h | 2 +-
gcc/testsuite/jit.dg/jit.exp | 7 +-
gcc/testsuite/jit.dg/test-asm.c | 13 +
gcc/testsuite/jit.dg/test-asm.cc | 12 +
gcc/testsuite/obj-c++.dg/pr101666-0.mm | 7 +
gcc/testsuite/obj-c++.dg/pr101666-1.mm | 10 +
gcc/testsuite/obj-c++.dg/pr101666.inc | 29 ++
gcc/testsuite/objc.dg/pr101666-0.m | 7 +
gcc/testsuite/objc.dg/pr101666-1.m | 10 +
gcc/testsuite/objc.dg/pr101666.inc | 29 ++
libgomp/ChangeLog | 20 ++
libiberty/ChangeLog | 5 +
libiberty/simple-object-mach-o.c | 5 +
libstdc++-v3/ChangeLog | 62 ++++
libstdc++-v3/doc/doxygen/user.cfg.in | 20 +-
libstdc++-v3/include/bits/stl_algo.h | 86 ++++--
libstdc++-v3/include/bits/stl_function.h | 134 ++++----
libstdc++-v3/include/bits/unique_ptr.h | 84 +++--
libstdc++-v3/include/debug/deque | 7 +-
libstdc++-v3/include/debug/forward_list | 7 +-
libstdc++-v3/include/debug/list | 7 +-
libstdc++-v3/include/debug/vector | 7 +-
libstdc++-v3/include/ext/type_traits.h | 16 +-
libstdc++-v3/include/std/complex | 29 --
libstdc++-v3/include/std/type_traits | 55 +++-
libstdc++-v3/python/libstdcxx/v6/printers.py | 10 +-
.../testsuite/libstdc++-prettyprinters/simple.cc | 14 +-
.../testsuite/libstdc++-prettyprinters/simple11.cc | 14 +-
90 files changed, 2120 insertions(+), 311 deletions(-)
next reply other threads:[~2021-08-19 10:03 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 10:03 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 11:37 Martin Liska
2022-11-07 8:55 Martin Liska
2022-11-07 7:25 Martin Liska
2022-10-28 8:02 Martin Liska
2022-10-26 10:59 Martin Liska
2022-10-21 10:48 Martin Liska
2022-10-19 13:25 Martin Liska
2022-10-17 8:20 Martin Liska
2022-10-15 13:33 Martin Liska
2022-10-13 13:54 Martin Liska
2022-10-08 8:19 Martin Liska
2022-10-04 10:05 Martin Liska
2022-09-29 8:41 Martin Liska
2022-09-26 19:06 Martin Liska
2022-09-20 15:24 Martin Liska
2022-09-20 12:03 Martin Liska
2022-09-20 11:53 Martin Liska
2022-09-12 8:43 Martin Liska
2022-09-06 4:52 Martin Liska
2022-09-05 9:22 Martin Liska
2022-09-05 8:45 Martin Liska
2022-08-24 8:10 Martin Liska
2022-08-10 7:18 Martin Liska
2022-08-09 13:30 Martin Liska
2022-08-08 7:05 Martin Liska
2022-08-01 3:54 Martin Liska
2022-07-26 12:28 Martin Liska
2022-07-26 12:09 Martin Liska
2022-07-26 8:04 Martin Liska
2022-07-25 7:01 Martin Liska
2022-07-21 14:12 Martin Liska
2022-07-19 13:41 Martin Liska
2022-07-18 7:51 Martin Liska
2022-07-14 9:34 Martin Liska
2022-07-14 8:35 Martin Liska
2022-07-14 8:23 Martin Liska
2022-07-12 11:24 Martin Liska
2022-07-10 14:45 Martin Liska
2022-06-17 11:35 Martin Liska
2022-06-17 11:06 Martin Liska
2022-03-15 9:13 Martin Liska
2022-03-10 9:42 Martin Liska
2022-03-06 15:29 Martin Liska
2022-01-28 13:08 Martin Liska
2022-01-24 12:35 Martin Liska
2022-01-20 12:38 Martin Liska
2022-01-18 14:25 Martin Liska
2022-01-12 12:35 Martin Liska
2022-01-03 19:33 Martin Liska
2022-01-03 10:16 Martin Liska
2021-12-30 13:34 Martin Liska
2021-12-29 12:43 Martin Liska
2021-12-28 10:14 Martin Liska
2021-12-28 10:06 Martin Liska
2021-12-22 11:17 Martin Liska
2021-12-22 11:08 Martin Liska
2021-12-22 11:03 Martin Liska
2021-12-20 10:01 Martin Liska
2021-12-17 14:04 Martin Liska
2021-12-16 14:23 Martin Liska
2021-12-16 13:11 Martin Liska
2021-12-13 10:57 Martin Liska
2021-12-12 21:22 Martin Liska
2021-12-09 10:39 Martin Liska
2021-12-01 12:31 Martin Liska
2021-11-25 12:26 Martin Liska
2021-11-23 10:28 Martin Liska
2021-11-22 16:39 Martin Liska
2021-11-22 12:58 Martin Liska
2021-11-16 14:50 Martin Liska
2021-10-21 9:51 Martin Liska
2021-10-18 12:43 Martin Liska
2021-08-27 8:52 Martin Liska
2021-08-26 9:23 Martin Liska
2021-08-24 14:43 Martin Liska
2021-08-24 7:30 Martin Liska
2021-08-23 13:42 Martin Liska
2021-08-23 10:35 Martin Liska
2021-08-18 14:13 Martin Liska
2021-08-10 7:12 Martin Liska
2021-08-09 9:15 Martin Liska
2021-08-06 10:38 Martin Liska
2021-08-05 17:50 Martin Liska
2021-08-03 13:50 Martin Liska
2021-07-12 9:41 Martin Liska
2021-06-30 4:49 Martin Liska
2021-06-29 6:49 Martin Liska
2021-06-28 11:11 Martin Liska
2021-06-25 8:52 Martin Liska
2021-06-24 14:10 Martin Liska
2021-06-23 8:20 Martin Liska
2021-06-22 7:48 Martin Liska
2021-06-21 7:33 Martin Liska
2021-06-17 10:06 Martin Liska
2021-06-16 12:19 Martin Liska
2021-06-15 12:35 Martin Liska
2021-06-14 14:08 Martin Liska
2021-06-14 14:05 Martin Liska
2021-06-14 13:38 Martin Liska
2021-06-14 9:40 Martin Liska
2021-06-11 11:03 Martin Liska
2021-06-10 6:22 Martin Liska
2021-06-09 11:40 Martin Liska
2021-06-08 7:47 Martin Liska
2021-06-07 13:38 Martin Liska
2021-06-06 14:57 Martin Liska
2021-06-04 11:37 Martin Liska
2021-06-03 10:53 Martin Liska
2021-06-02 12:46 Martin Liska
2021-06-02 6:59 Martin Liska
2021-05-31 9:31 Martin Liska
2021-05-28 12:29 Martin Liska
2021-05-27 7:52 Martin Liska
2021-05-26 7:35 Martin Liska
2021-05-26 7:29 Martin Liska
2021-05-25 13:01 Martin Liska
2021-05-24 9:40 Martin Liska
2021-05-18 9:25 Martin Liska
2021-05-17 13:53 Martin Liska
2021-05-11 17:33 Martin Liska
2021-04-22 7:11 Martin Liska
2021-04-20 8:02 Martin Liska
2021-04-19 11:44 Martin Liska
2021-04-15 12:51 Martin Liska
2021-04-14 10:30 Martin Liska
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=20210819100340.9DE85382CC36@sourceware.org \
--to=marxin@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: 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).