public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-12] Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Mon,  6 Feb 2023 07:42:15 +0000 (GMT)	[thread overview]
Message-ID: <20230206074215.BECC03858C1F@sourceware.org> (raw)

https://gcc.gnu.org/g:d4309091390bebf46c7e56cba35bd88ad7d8b9ef

commit d4309091390bebf46c7e56cba35bd88ad7d8b9ef
Merge: 07cea1a91b4 cbebc0a753d
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Mon Feb 6 08:41:27 2023 +0100

    Merge branch 'releases/gcc-12' into devel/omp/gcc-12
    
    Merge up to r12-9109-gcbebc0a753d404a064f8e306374627573ef2deb6 (6th Feb 2023)

Diff:

 gcc/DATESTAMP                                    |  2 +-
 gcc/cp/ChangeLog                                 |  9 ++++
 gcc/cp/semantics.cc                              | 15 ++++--
 gcc/fortran/ChangeLog                            | 40 ++++++++++++++++
 gcc/fortran/check.cc                             |  2 +
 gcc/fortran/expr.cc                              |  6 ++-
 gcc/fortran/match.cc                             | 10 ++++
 gcc/fortran/resolve.cc                           | 29 ++++++------
 gcc/testsuite/ChangeLog                          | 41 ++++++++++++++++
 gcc/testsuite/g++.dg/template/call9.C            | 26 +++++++++++
 gcc/testsuite/gfortran.dg/common_27.f90          | 14 ++++++
 gcc/testsuite/gfortran.dg/gomp/minmaxloc_1.f90   | 32 +++++++++++++
 gcc/testsuite/gfortran.dg/pr108527.f90           | 10 ++++
 libstdc++-v3/ChangeLog                           | 59 ++++++++++++++++++++++++
 libstdc++-v3/config/os/generic/error_constants.h |  2 +
 libstdc++-v3/include/bits/atomic_wait.h          |  8 ++--
 libstdc++-v3/include/bits/regex_automaton.h      |  2 +-
 libstdc++-v3/include/bits/regex_error.h          | 26 +++++------
 libstdc++-v3/include/ext/concurrence.h           |  2 +-
 libstdc++-v3/include/pstl/execution_defs.h       |  8 ++--
 libstdc++-v3/src/c++11/random.cc                 |  2 +
 libstdc++-v3/src/c++11/system_error.cc           |  9 ++++
 libstdc++-v3/src/c++17/fs_ops.cc                 |  6 ++-
 libstdc++-v3/src/filesystem/ops-common.h         |  2 +-
 24 files changed, 315 insertions(+), 47 deletions(-)

             reply	other threads:[~2023-02-06  7:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  7:42 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-27 16:34 Tobias Burnus
2023-02-20  6:52 Tobias Burnus
2023-02-13  9:21 Tobias Burnus
2023-01-19 20:24 Tobias Burnus
2023-01-09  9:21 Tobias Burnus
2022-12-27 10:54 Tobias Burnus
2022-12-21 18:21 Tobias Burnus
2022-12-19 17:32 Tobias Burnus
2022-11-25 10:37 Tobias Burnus
2022-11-18  9:48 Tobias Burnus
2022-11-14 15:41 Tobias Burnus
2022-10-24 10:21 Tobias Burnus
2022-10-11  8:26 Tobias Burnus
2022-09-29 14:45 Tobias Burnus
2022-09-23  8:48 Tobias Burnus
2022-09-09 13:39 Tobias Burnus
2022-08-31  6:14 Tobias Burnus
2022-07-28 13:29 Tobias Burnus
2022-07-28 13:29 Tobias Burnus
2022-07-01 18:13 Kwok Yeung

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=20230206074215.BECC03858C1F@sourceware.org \
    --to=burnus@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).