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-13] Merge branch 'releases/gcc-13' into devel/omp/gcc-13
Date: Fri,  8 Sep 2023 11:19:37 +0000 (GMT)	[thread overview]
Message-ID: <20230908111937.7A4A33858C2D@sourceware.org> (raw)

https://gcc.gnu.org/g:7496d88c2c6b3c2da7ca167804c4a64dba358cf4

commit 7496d88c2c6b3c2da7ca167804c4a64dba358cf4
Merge: 9f7bff64a532 65e2ddf4f33b
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Sep 8 13:18:49 2023 +0200

    Merge branch 'releases/gcc-13' into devel/omp/gcc-13
    
    Merge up to r13-7780-g65e2ddf4f33b5bf42021bc8b2e37e1eecd43e152 (8th Sep 2023)

Diff:

 gcc/ChangeLog                                      |  50 +++++++++
 gcc/DATESTAMP                                      |   2 +-
 gcc/config/loongarch/loongarch.cc                  |   4 +-
 gcc/config/riscv/riscv-vsetvl.cc                   |   5 +
 gcc/config/riscv/riscv.cc                          |  13 ++-
 gcc/cp/ChangeLog                                   |  12 +++
 gcc/cp/cp-tree.h                                   |   1 +
 gcc/cp/decl.cc                                     |   2 +
 gcc/cp/pt.cc                                       |   3 -
 gcc/cp/typeck.cc                                   |   3 +
 gcc/fortran/ChangeLog                              |  11 ++
 gcc/fortran/parse.cc                               |  63 +++++++-----
 gcc/fortran/resolve.cc                             |   3 +-
 gcc/gimple-ssa-store-merging.cc                    |   9 +-
 gcc/testsuite/ChangeLog                            |  57 +++++++++++
 gcc/testsuite/g++.dg/cpp2a/concepts-friend11.C     |   3 +-
 gcc/testsuite/g++.dg/cpp2a/concepts-friend15.C     |  22 ++++
 gcc/testsuite/g++.dg/opt/nrv22.C                   |  30 ++++++
 gcc/testsuite/gcc.c-torture/execute/pr110914.c     |  22 ++++
 gcc/testsuite/gcc.dg/pr111015.c                    |  28 +++++
 .../gcc.target/riscv/rvv/base/scalar_move-10.c     |  31 ++++++
 .../gcc.target/riscv/rvv/base/scalar_move-11.c     |  20 ++++
 gcc/testsuite/gfortran.dg/associate_54.f90         |   2 +-
 gcc/testsuite/gfortran.dg/pr102109.f90             |  20 ++++
 gcc/testsuite/gfortran.dg/pr102112.f90             |  23 +++++
 gcc/testsuite/gfortran.dg/pr102190.f90             |  74 +++++++++++++
 gcc/testsuite/gfortran.dg/pr102532.f90             |  16 +++
 gcc/testsuite/gfortran.dg/pr109948.f90             | 114 +++++++++++++++++++++
 gcc/testsuite/gfortran.dg/pr99326.f90              |  26 +++++
 gcc/tree-ssa-strlen.cc                             |   3 +-
 30 files changed, 627 insertions(+), 45 deletions(-)

             reply	other threads:[~2023-09-08 11:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 11:19 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-08-25  9:58 Tobias Burnus
2023-08-18 10:49 Tobias Burnus
2023-07-27 10:37 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=20230908111937.7A4A33858C2D@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: 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).