public inbox for gcc-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, 9 Jan 2023 09:21:34 +0000 (GMT) [thread overview] Message-ID: <20230109092134.0E6E83858D20@sourceware.org> (raw) https://gcc.gnu.org/g:1624a774fad595d9744bd2ace1244a670bca653e commit 1624a774fad595d9744bd2ace1244a670bca653e Merge: 9795d3d7ff6 4494965932f Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Jan 9 10:20:42 2023 +0100 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Merge up to r12-9034-g4494965932fc5d005e2482bbe58cf9e138c830bd (9th Jan 2023) Diff: gcc/ChangeLog | 13 ++++++ gcc/DATESTAMP | 2 +- gcc/config/rs6000/mma.md | 10 ++++- gcc/config/rs6000/rs6000-protos.h | 2 + gcc/config/rs6000/rs6000.cc | 39 ++++++++++++++++- gcc/cp/ChangeLog | 9 ++++ gcc/cp/decl2.cc | 2 +- gcc/fortran/ChangeLog | 10 +++++ gcc/fortran/array.cc | 4 -- gcc/testsuite/ChangeLog | 26 ++++++++++++ gcc/testsuite/g++.dg/cpp2a/concepts-requires34.C | 19 +++++++++ gcc/testsuite/gcc.target/powerpc/pr106736-1.c | 20 +++++++++ gcc/testsuite/gcc.target/powerpc/pr106736-2.c | 17 ++++++++ gcc/testsuite/gcc.target/powerpc/pr106736-3.c | 18 ++++++++ gcc/testsuite/gcc.target/powerpc/pr106736-4.c | 19 +++++++++ gcc/testsuite/gcc.target/powerpc/pr106736-5.c | 18 ++++++++ gcc/testsuite/gfortran.dg/pr103505.f90 | 8 ++-- gcc/testsuite/gfortran.dg/pr108131.f90 | 25 +++++++++++ libiberty/ChangeLog | 14 ++++++ libiberty/acinclude.m4 | 14 ++++-- libiberty/configure | 14 ++++-- libsanitizer/ChangeLog | 9 ++++ libsanitizer/configure | 1 + libsanitizer/configure.ac | 3 +- libstdc++-v3/ChangeLog | 11 +++++ libstdc++-v3/include/std/chrono | 38 +++++++++++------ libstdc++-v3/testsuite/std/time/hh_mm_ss/1.cc | 54 +++++++++++++++++++++++- 27 files changed, 387 insertions(+), 32 deletions(-)
next reply other threads:[~2023-01-09 9:21 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-09 9:21 Tobias Burnus [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-03-02 15:33 Tobias Burnus 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-02-02 9:20 Tobias Burnus 2023-01-30 9:11 Tobias Burnus 2023-01-26 10:22 Tobias Burnus 2023-01-23 8:29 Tobias Burnus 2023-01-19 20:24 Tobias Burnus 2023-01-16 11:27 Tobias Burnus 2022-12-27 10:54 Tobias Burnus 2022-12-21 18:21 Tobias Burnus 2022-12-19 17:32 Tobias Burnus 2022-12-12 14:26 Tobias Burnus 2022-12-09 8:39 Tobias Burnus 2022-12-01 7:40 Tobias Burnus 2022-11-25 10:37 Tobias Burnus 2022-11-21 14:29 Tobias Burnus 2022-11-18 9:48 Tobias Burnus 2022-11-14 15:41 Tobias Burnus 2022-11-04 12:50 Tobias Burnus 2022-11-02 8:07 Tobias Burnus 2022-10-27 12:39 Tobias Burnus 2022-10-24 10:21 Tobias Burnus 2022-10-18 9:12 Tobias Burnus 2022-10-11 8:26 Tobias Burnus 2022-09-29 14:45 Tobias Burnus 2022-09-28 7:53 Tobias Burnus 2022-09-23 8:48 Tobias Burnus 2022-09-09 13:39 Tobias Burnus 2022-09-05 8:19 Tobias Burnus 2022-08-31 6:14 Tobias Burnus 2022-08-03 12:17 Tobias Burnus 2022-08-01 13:03 Tobias Burnus 2022-07-28 13:29 Tobias Burnus 2022-07-28 13:29 Tobias Burnus 2022-07-05 10:32 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=20230109092134.0E6E83858D20@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: 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).