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, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/c++-coroutines] Merge master r12-6020.
Date: Thu, 16 Dec 2021 20:17:10 +0000 (GMT)	[thread overview]
Message-ID: <20211216201710.694DB3858015@sourceware.org> (raw)

https://gcc.gnu.org/g:7f4b905eedb06194bf83e58d2fef2e43f3aaf17b

commit 7f4b905eedb06194bf83e58d2fef2e43f3aaf17b
Merge: 9578717495c 06cd44b4387
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Thu Dec 16 17:30:58 2021 +0000

    Merge master r12-6020.
    
            * Merge master r12-6020-g06cd44b4387a.

Diff:

 ChangeLog                                          |   32 +
 Makefile.in                                        |   63 +-
 Makefile.tpl                                       |   63 +-
 config.sub                                         |    2 +-
 config/ChangeLog                                   |    8 +
 configure                                          |  100 +-
 configure.ac                                       |   65 +
 contrib/analyze_brprob_spec.py                     |    1 +
 gcc/ChangeLog                                      |  169 ++
 gcc/DATESTAMP                                      |    2 +-
 gcc/attribs.c                                      |    3 +-
 gcc/c-family/c-pragma.c                            |    2 +-
 gcc/config/aarch64/aarch64-simd.md                 |    5 +-
 gcc/config/rs6000/rs6000-c.c                       | 1717 +++++++++++---------
 gcc/cp/ChangeLog                                   |   18 +
 gcc/cp/decl.c                                      |   58 +-
 gcc/cp/pt.c                                        |   13 -
 gcc/d/ChangeLog                                    |    6 +
 gcc/doc/invoke.texi                                |    2 +-
 gcc/gcc.c                                          |   25 +-
 gcc/testsuite/ChangeLog                            |   85 +
 gcc/testsuite/g++.dg/cpp1y/decltype-auto5.C        |   35 +
 gcc/testsuite/g++.target/i386/pr103696.C           |   25 +
 gcc/testsuite/gfortran.dg/date_and_time_1.f90      |   35 +
 gcc/testsuite/gfortran.dg/iostat_5.f90             |   16 +
 gcc/testsuite/lib/fortran-torture.exp              |    8 +-
 gcc/testsuite/lib/gcc-defs.exp                     |    4 +-
 gcc/testsuite/lib/gcc-dg.exp                       |    6 +-
 gcc/testsuite/lib/go-torture.exp                   |    8 +-
 libcc1/ChangeLog                                   |    4 +
 libgfortran/intrinsics/date_and_time.c             |   24 +-
 libgfortran/intrinsics/time_1.h                    |   14 +-
 libgfortran/io/file_pos.c                          |    2 +-
 libiberty/ChangeLog                                |   10 +
 libphobos/ChangeLog                                |   10 +
 libstdc++-v3/ChangeLog                             |   22 +
 libstdc++-v3/include/bits/stl_iterator.h           |   32 +-
 libstdc++-v3/include/debug/safe_iterator.h         |   17 +
 .../24_iterators/normal_iterator/to_address.cc     |   17 +-
 zlib/ChangeLog                                     |    4 +
 40 files changed, 1847 insertions(+), 885 deletions(-)


                 reply	other threads:[~2021-12-16 20:17 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=20211216201710.694DB3858015@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: 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).