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-13] Merge branch 'releases/gcc-13' into devel/omp/gcc-13 Date: Thu, 27 Jul 2023 10:37:47 +0000 (GMT) [thread overview] Message-ID: <20230727103747.64D8A385B525@sourceware.org> (raw) https://gcc.gnu.org/g:58718b8dc2f64342e3311e60b89896825a9817e7 commit 58718b8dc2f64342e3311e60b89896825a9817e7 Merge: 087feef19a9 f1d4b4f918a Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Jul 27 12:33:47 2023 +0200 Merge branch 'releases/gcc-13' into devel/omp/gcc-13 Merge up to r13-7610-gf1d4b4f918a9c5b25a82b7bfccb08aa5e647f41c (27th July 2021) This is the GCC 13.2.0 release except for the follow-up commit "Bump BASE-VER" which sets the version to 13.2.1 to denote post-release branch development. Diff: ChangeLog | 4 + c++tools/ChangeLog | 4 + config/ChangeLog | 4 + contrib/ChangeLog | 4 + contrib/header-tools/ChangeLog | 4 + contrib/reghunt/ChangeLog | 4 + contrib/regression/ChangeLog | 4 + fixincludes/ChangeLog | 4 + gcc/BASE-VER | 2 +- gcc/ChangeLog | 4 + gcc/DATESTAMP | 2 +- gcc/ada/ChangeLog | 4 + gcc/analyzer/ChangeLog | 4 + gcc/c-family/ChangeLog | 4 + gcc/c/ChangeLog | 4 + gcc/cp/ChangeLog | 4 + gcc/d/ChangeLog | 4 + gcc/fortran/ChangeLog | 4 + gcc/go/ChangeLog | 4 + gcc/jit/ChangeLog | 4 + gcc/lto/ChangeLog | 4 + gcc/m2/ChangeLog | 4 + gcc/objc/ChangeLog | 4 + gcc/objcp/ChangeLog | 4 + gcc/po/ChangeLog | 20 + gcc/po/gcc.pot | 6426 +++---- gcc/po/hr.po | 18 +- gcc/po/uk.po | 32405 ++++++++++++++++++------------------ gcc/rust/ChangeLog | 4 + gcc/testsuite/ChangeLog | 4 + gnattools/ChangeLog | 4 + gotools/ChangeLog | 4 + include/ChangeLog | 4 + intl/ChangeLog | 4 + libada/ChangeLog | 4 + libatomic/ChangeLog | 4 + libbacktrace/ChangeLog | 4 + libcc1/ChangeLog | 4 + libcody/ChangeLog | 4 + libcpp/ChangeLog | 4 + libcpp/po/ChangeLog | 4 + libdecnumber/ChangeLog | 4 + libffi/ChangeLog | 4 + libgcc/ChangeLog | 4 + libgcc/config/avr/libf7/ChangeLog | 4 + libgcc/config/libbid/ChangeLog | 4 + libgfortran/ChangeLog | 4 + libgm2/ChangeLog | 4 + libgomp/ChangeLog | 4 + libiberty/ChangeLog | 4 + libitm/ChangeLog | 4 + libobjc/ChangeLog | 4 + libphobos/ChangeLog | 4 + libquadmath/ChangeLog | 4 + libsanitizer/ChangeLog | 4 + libssp/ChangeLog | 4 + libstdc++-v3/ChangeLog | 4 + libvtv/ChangeLog | 4 + lto-plugin/ChangeLog | 4 + maintainer-scripts/ChangeLog | 4 + zlib/ChangeLog | 4 + 61 files changed, 19839 insertions(+), 19254 deletions(-)
next reply other threads:[~2023-07-27 10:37 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 10:37 Tobias Burnus [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-10-26 14:14 Tobias Burnus 2023-10-17 8:38 Tobias Burnus 2023-10-06 8:03 Tobias Burnus 2023-09-29 12:29 Tobias Burnus 2023-09-18 7:29 Tobias Burnus 2023-09-08 11:19 Tobias Burnus 2023-08-25 9:58 Tobias Burnus 2023-08-18 10:49 Tobias Burnus 2023-07-10 11:09 Tobias Burnus 2023-06-22 13:19 Tobias Burnus 2023-06-14 16:26 Tobias Burnus 2023-06-12 16:55 Tobias Burnus 2023-06-09 11:19 Tobias Burnus 2023-05-22 19:59 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=20230727103747.64D8A385B525@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).