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: Fri,  9 Sep 2022 13:39:53 +0000 (GMT)	[thread overview]
Message-ID: <20220909133953.7ACBE385742A@sourceware.org> (raw)

https://gcc.gnu.org/g:0010ad7047c47e6ee7fb469753d8776ae8d9b9b3

commit 0010ad7047c47e6ee7fb469753d8776ae8d9b9b3
Merge: de28004fa5f 4ce316ca54c
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Sep 9 15:38:50 2022 +0200

    Merge branch 'releases/gcc-12' into devel/omp/gcc-12
    
    Merge up to r12-8753-g4ce316ca54c863cf0fd4257ba0ab768ab83c62e5 (9th Sep 2022)

Diff:

 gcc/ChangeLog                                      |  7 +++
 gcc/DATESTAMP                                      |  2 +-
 gcc/config/rs6000/rtems.h                          |  3 +-
 gcc/config/rs6000/t-rtems                          |  5 ++
 gcc/fortran/ChangeLog                              |  9 ++++
 gcc/fortran/trans-expr.cc                          |  7 ++-
 gcc/testsuite/ChangeLog                            |  8 +++
 gcc/testsuite/g++.dg/opt/pr106860.C                | 23 +++++++++
 gcc/testsuite/g++.dg/vect/pr106841.cc              | 52 ++++++++++++++++++++
 gcc/testsuite/gcc.dg/torture/pr106809.c            | 28 +++++++++++
 gcc/testsuite/gfortran.dg/PR100136.f90             | 39 +++++++++++++++
 gcc/tree-ssa-loop-split.cc                         | 16 +++---
 gcc/tree-ssa-sccvn.cc                              | 57 ++++++++++++----------
 gcc/tree-vect-slp.cc                               |  9 ++++
 libstdc++-v3/ChangeLog                             | 26 ++++++++++
 libstdc++-v3/include/bits/regex_compiler.tcc       | 10 ++--
 libstdc++-v3/include/bits/std_thread.h             |  8 ++-
 libstdc++-v3/include/std/future                    |  4 +-
 .../testsuite/28_regex/basic_regex/106607.cc       | 25 ++++++++++
 libstdc++-v3/testsuite/30_threads/async/106695.cc  | 29 +++++++++++
 libstdc++-v3/testsuite/30_threads/thread/106695.cc | 21 ++++++++
 21 files changed, 342 insertions(+), 46 deletions(-)

             reply	other threads:[~2022-09-09 13:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 13:39 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-02-06  7:42 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-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=20220909133953.7ACBE385742A@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).