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 Subject: [gcc/devel/omp/gcc-12] Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Tue, 18 Oct 2022 09:12:53 +0000 (GMT) [thread overview] Message-ID: <20221018091253.550DC3857BB4@sourceware.org> (raw) https://gcc.gnu.org/g:764db096e7f6f984d24ed0bfd03c4a6a2ad4fa78 commit 764db096e7f6f984d24ed0bfd03c4a6a2ad4fa78 Merge: cc4b1e41c76 912bdd5cfb9 Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue Oct 18 10:00:17 2022 +0200 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Merge up to r12-8843-g912bdd5cfb92f6dd58accd755ad14f47c0df619e (18th Oct 2022) Diff: gcc/ChangeLog | 157 ++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/config/arm/mve.md | 30 +-- gcc/config/rs6000/rs6000-call.cc | 6 + gcc/config/sparc/sparc.cc | 24 +-- gcc/cp/ChangeLog | 9 + gcc/cp/except.cc | 7 +- gcc/fortran/ChangeLog | 31 ++++ gcc/fortran/trans-expr.cc | 65 ++++--- gcc/fortran/trans.h | 3 +- gcc/testsuite/ChangeLog | 115 ++++++++++++ gcc/testsuite/g++.dg/cpp0x/initlist-defarg3.C | 13 ++ gcc/testsuite/g++.dg/torture/pr106922.C | 48 +++++ gcc/testsuite/g++.dg/tree-ssa/pr106922.C | 90 +++++++++ gcc/testsuite/g++.dg/uninit-pr105937.C | 235 ++++++++++++++++++++++++ gcc/testsuite/gcc.dg/pr107107.c | 25 +++ gcc/testsuite/gcc.dg/torture/pr106892.c | 30 +++ gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c | 25 +++ gcc/testsuite/gcc.dg/vect/pr107160.c | 41 +++++ gcc/testsuite/gcc.dg/vect/pr107212-1.c | 27 +++ gcc/testsuite/gcc.dg/vect/pr107212-2.c | 23 +++ gcc/testsuite/gfortran.dg/intent_optimize_4.f90 | 43 +++++ gcc/testsuite/gfortran.dg/intent_out_15.f90 | 27 +++ gcc/testsuite/gfortran.dg/pr106934.f90 | 7 + gcc/testsuite/gfortran.dg/vect/pr107254.f90 | 49 +++++ gcc/tree-predcom.cc | 18 +- gcc/tree-ssa-pre.cc | 18 +- gcc/tree-ssa-sccvn.cc | 118 +++++++----- gcc/tree-ssa-uninit.cc | 14 +- gcc/tree-ssa.cc | 6 + gcc/tree-vect-loop.cc | 23 ++- gcc/tree-vect-slp.cc | 33 +++- 32 files changed, 1234 insertions(+), 128 deletions(-)
next reply other threads:[~2022-10-18 9:12 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-18 9:12 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 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-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-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=20221018091253.550DC3857BB4@sourceware.org \ --to=burnus@gcc.gnu.org \ --cc=gcc-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).