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: Tue, 11 Oct 2022 08:26:25 +0000 (GMT) [thread overview]
Message-ID: <20221011082625.26C233858289@sourceware.org> (raw)
https://gcc.gnu.org/g:b3f25511fb4bd4dbfc4068df665f4ea34f416b2d
commit b3f25511fb4bd4dbfc4068df665f4ea34f416b2d
Merge: d8909f7d242 97374f25e1e
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Tue Oct 11 10:13:28 2022 +0200
Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Merge up to r12-8817-g97374f25e1ee7ea45293c244f29425c9f9abcf5a (11th Oct 2022)
Diff:
gcc/ChangeLog | 30 +
gcc/DATESTAMP | 2 +-
gcc/config/i386/predicates.md | 20 +-
gcc/config/i386/sse.md | 4 +-
gcc/config/i386/t-i386 | 5 +
gcc/cp/ChangeLog | 4 +
gcc/cp/class.cc | 13 +-
gcc/fortran/ChangeLog | 60 ++
gcc/fortran/expr.cc | 3 +-
gcc/fortran/simplify.cc | 13 +-
gcc/fortran/trans-array.cc | 4 +-
gcc/fortran/trans-decl.cc | 1 +
gcc/fortran/trans-expr.cc | 48 +-
gcc/fortran/trans-types.cc | 15 +-
gcc/po/ChangeLog | 4 +
gcc/po/sv.po | 36 +-
gcc/testsuite/ChangeLog | 73 ++
gcc/testsuite/g++.dg/cpp2a/cond-triv3.C | 44 +
.../gcc.target/i386/keylocker-encodekey128.c | 1 -
.../gcc.target/i386/keylocker-encodekey256.c | 1 -
gcc/testsuite/gfortran.dg/PR100029.f90 | 22 +
gcc/testsuite/gfortran.dg/PR100040.f90 | 36 +
gcc/testsuite/gfortran.dg/PR100103.f90 | 76 ++
gcc/testsuite/gfortran.dg/PR100132.f90 | 75 ++
gcc/testsuite/gfortran.dg/associate_26a.f90 | 15 +
gcc/testsuite/gfortran.dg/pr106985.f90 | 8 +
gcc/testsuite/gfortran.dg/pr107054.f90 | 13 +
libcpp/po/ChangeLog | 4 +
libcpp/po/ro.po | 1140 ++++++++++++++++++++
libstdc++-v3/ChangeLog | 21 +
30 files changed, 1728 insertions(+), 63 deletions(-)
next reply other threads:[~2022-10-11 8:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 8:26 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-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=20221011082625.26C233858289@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).