public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Gaius Mulley <gaius@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc/devel/modula-2] Merge branch 'master' into devel/modula-2. Date: Thu, 28 Apr 2022 15:14:53 +0000 (GMT) [thread overview] Message-ID: <20220428151453.B1BF83856277@sourceware.org> (raw) https://gcc.gnu.org/g:e684d1aa612f2b673488cd7c5f269d45e8048476 commit e684d1aa612f2b673488cd7c5f269d45e8048476 Merge: 9506c9f1ab1 2a570f11a2f Author: Gaius Mulley <gaius.mulley@southwales.ac.uk> Date: Thu Apr 28 15:02:23 2022 +0100 Merge branch 'master' into devel/modula-2. Diff: gcc/ChangeLog | 44 ++++++ gcc/DATESTAMP | 2 +- gcc/ada/ChangeLog | 11 ++ gcc/ada/tracebak.c | 32 ++--- gcc/config/i386/i386.cc | 1 + gcc/config/loongarch/loongarch.cc | 3 + gcc/config/loongarch/loongarch.md | 46 +++++-- gcc/cp/ChangeLog | 9 ++ gcc/cp/coroutines.cc | 66 +++++---- gcc/cp/parser.cc | 1 + gcc/cp/pt.cc | 2 +- gcc/cp/tree.cc | 3 +- gcc/d/d-port.cc | 8 +- gcc/d/dmd/MERGE | 2 +- gcc/d/dmd/cparse.d | 95 ++++++++++--- gcc/d/dmd/dscope.d | 2 + gcc/d/dmd/expression.h | 6 +- gcc/d/dmd/expressionsem.d | 29 +++- gcc/d/dmd/root/port.h | 5 +- gcc/doc/install.texi | 25 ++-- gcc/fortran/ChangeLog | 16 +++ gcc/fortran/array.cc | 27 ++-- gcc/fortran/trans-array.cc | 7 +- gcc/gimple-ssa-warn-access.cc | 7 +- gcc/testsuite/ChangeLog | 61 +++++++++ gcc/testsuite/g++.dg/coroutines/pr103868.C | 150 +++++++++++++++++++++ gcc/testsuite/g++.dg/coroutines/pr104051.C | 29 ++++ gcc/testsuite/g++.dg/coroutines/pr105287.C | 48 +++++++ gcc/testsuite/g++.dg/coroutines/pr105301.C | 49 +++++++ gcc/testsuite/g++.dg/cpp1y/lambda-generic-enum2.C | 15 +++ gcc/testsuite/g++.dg/parse/qualified6.C | 10 ++ gcc/testsuite/g++.dg/warn/pr104492.C | 115 ++++++++++++++++ gcc/testsuite/g++.target/i386/mv31.C | 1 + gcc/testsuite/gcc.dg/pr105331.c | 11 ++ gcc/testsuite/gcc.dg/torture/pr104676.c | 2 +- gcc/testsuite/gcc.dg/vect/pr105219.c | 29 ++++ gcc/testsuite/gcc.target/i386/memcpy-strategy-10.c | 4 +- gcc/testsuite/gcc.target/i386/memcpy-strategy-5.c | 4 +- gcc/testsuite/gcc.target/i386/memset-strategy-5.c | 4 +- gcc/testsuite/gcc.target/i386/memset-strategy-7.c | 4 +- .../gcc.target/loongarch/zero-size-field-pass.c | 30 +++++ .../gcc.target/loongarch/zero-size-field-ret.c | 28 ++++ gcc/testsuite/gcc.target/powerpc/pr105334.c | 31 +++++ gcc/testsuite/gdc.test/compilable/revert_dip1000.d | 7 + .../gfortran.dg/character_array_dummy_1.f90 | 21 +++ gcc/testsuite/gfortran.dg/class_dummy_8.f90 | 20 +++ gcc/testsuite/gfortran.dg/class_dummy_9.f90 | 20 +++ gcc/testsuite/gfortran.dg/pr70673.f90 | 2 - gcc/testsuite/gfortran.dg/pr70673_2.f90 | 25 ++++ gcc/tree-vect-loop.cc | 6 +- libgomp/testsuite/libgomp.oacc-fortran/print-1.f90 | 30 ++++- libphobos/libdruntime/MERGE | 2 +- libstdc++-v3/ChangeLog | 21 +++ .../post/aarch64-linux-gnu/baseline_symbols.txt | 12 +- .../abi/post/i486-linux-gnu/baseline_symbols.txt | 12 +- .../post/powerpc-linux-gnu/baseline_symbols.txt | 12 +- .../powerpc64-linux-gnu/32/baseline_symbols.txt | 12 +- .../post/powerpc64-linux-gnu/baseline_symbols.txt | 14 +- .../abi/post/s390x-linux-gnu/baseline_symbols.txt | 12 +- .../post/x86_64-linux-gnu/32/baseline_symbols.txt | 12 +- .../abi/post/x86_64-linux-gnu/baseline_symbols.txt | 12 +- .../config/abi/pre/gnu-versioned-namespace.ver | 1 - libstdc++-v3/python/libstdcxx/v6/printers.py | 53 +++++++- libstdc++-v3/src/c++17/fs_ops.cc | 8 +- libstdc++-v3/src/filesystem/ops.cc | 8 +- .../testsuite/27_io/filesystem/operations/copy.cc | 29 ++++ .../experimental/filesystem/operations/copy.cc | 29 ++++ .../testsuite/libstdc++-prettyprinters/cxx11.cc | 10 ++ .../testsuite/libstdc++-prettyprinters/cxx20.cc | 9 ++ 69 files changed, 1318 insertions(+), 155 deletions(-)
next reply other threads:[~2022-04-28 15:14 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 15:14 Gaius Mulley [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-12-14 12:30 Gaius Mulley 2022-12-07 19:51 Gaius Mulley 2022-12-01 0:32 Gaius Mulley 2022-11-18 12:25 Gaius Mulley 2022-11-15 23:00 Gaius Mulley 2022-11-02 23:24 Gaius Mulley 2022-10-22 1:58 Gaius Mulley 2022-10-12 12:57 Gaius Mulley 2022-10-04 11:47 Gaius Mulley 2022-09-26 11:40 Gaius Mulley 2022-09-20 15:20 Gaius Mulley 2022-09-14 18:58 Gaius Mulley 2022-09-12 20:46 Gaius Mulley 2022-09-08 15:03 Gaius Mulley 2022-09-02 15:27 Gaius Mulley 2022-08-29 13:42 Gaius Mulley 2022-08-25 22:53 Gaius Mulley 2022-08-12 8:40 Gaius Mulley 2022-08-08 12:01 Gaius Mulley 2022-07-29 16:23 Gaius Mulley 2022-07-26 0:28 Gaius Mulley 2022-07-11 23:17 Gaius Mulley 2022-07-06 20:03 Gaius Mulley 2022-05-30 13:25 Gaius Mulley 2022-05-23 22:02 Gaius Mulley 2022-05-20 1:41 Gaius Mulley 2022-05-15 22:44 Gaius Mulley 2022-05-12 9:02 Gaius Mulley 2022-05-10 11:05 Gaius Mulley 2022-05-06 12:28 Gaius Mulley 2022-05-05 19:37 Gaius Mulley 2022-05-03 12:08 Gaius Mulley 2022-04-29 20:01 Gaius Mulley 2022-04-29 15:22 Gaius Mulley 2022-04-27 11:17 Gaius Mulley 2022-04-26 17:23 Gaius Mulley 2022-04-25 19:40 Gaius Mulley 2022-04-22 8:09 Gaius Mulley 2022-04-20 11:35 Gaius Mulley 2022-04-01 19:20 Gaius Mulley 2022-03-24 23:10 Gaius Mulley 2022-03-16 20:33 Gaius Mulley 2022-03-02 18:47 Gaius Mulley 2022-02-14 17:00 Gaius Mulley 2022-02-05 13:34 Gaius Mulley 2022-01-29 11:11 Gaius Mulley 2022-01-25 18:58 Gaius Mulley 2022-01-21 20:48 Gaius Mulley 2022-01-20 12:42 Gaius Mulley 2022-01-18 13:54 Gaius Mulley 2022-01-14 0:26 Gaius Mulley 2022-01-06 21:41 Gaius Mulley 2021-12-19 1:19 Gaius Mulley 2021-12-09 21:59 Gaius Mulley 2021-11-27 13:22 Gaius Mulley 2021-11-19 18:30 Gaius Mulley 2021-11-07 15:22 Gaius Mulley 2021-10-27 8:45 Gaius Mulley 2021-10-19 22:57 Gaius Mulley 2021-10-08 14:03 Gaius Mulley 2021-09-16 12:03 Gaius Mulley 2021-09-14 11:39 Gaius Mulley 2021-09-02 15:49 Gaius Mulley 2021-08-27 0:43 Gaius Mulley 2021-08-18 14:24 Gaius Mulley 2021-08-10 13:57 Gaius Mulley 2021-07-28 18:59 Gaius Mulley
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=20220428151453.B1BF83856277@sourceware.org \ --to=gaius@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).