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: Thu, 22 Jun 2023 13:19:05 +0000 (GMT)	[thread overview]
Message-ID: <20230622131905.27756385773F@sourceware.org> (raw)

https://gcc.gnu.org/g:ed75061e019202b03ac32fbe2c78710ffa76c51f

commit ed75061e019202b03ac32fbe2c78710ffa76c51f
Merge: 50b2cd7e29e d116ce76105
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Jun 22 15:04:53 2023 +0200

    Merge branch 'releases/gcc-13' into devel/omp/gcc-13
    
    Merge up to r13-7464-gd116ce761052947efa392ae95c7ca6230147ac29 (22nd June 2023)

Diff:

 gcc/ChangeLog                                    | 91 ++++++++++++++++++++++++
 gcc/DATESTAMP                                    |  2 +-
 gcc/ada/ChangeLog                                |  9 +++
 gcc/ada/exp_ch5.adb                              |  1 +
 gcc/ada/sem_ch5.adb                              | 11 +--
 gcc/ada/sinfo.ads                                |  5 ++
 gcc/config/aarch64/aarch64-builtins.cc           | 88 +++++++++++++----------
 gcc/config/aarch64/aarch64.md                    | 24 +++----
 gcc/config/aarch64/arm_acle.h                    | 33 ---------
 gcc/config/loongarch/loongarch.md                |  8 ++-
 gcc/config/rs6000/rs6000-builtins.def            | 14 ++--
 gcc/config/rs6000/rs6000.cc                      |  2 +-
 gcc/ira-costs.cc                                 | 10 +++
 gcc/testsuite/ChangeLog                          | 57 +++++++++++++++
 gcc/testsuite/g++.target/aarch64/acle/acle.exp   | 35 +++++++++
 gcc/testsuite/g++.target/aarch64/acle/ls64.C     | 10 +++
 gcc/testsuite/g++.target/aarch64/acle/ls64_lto.C | 10 +++
 gcc/testsuite/gcc.target/aarch64/acle/ls64_lto.c | 10 +++
 gcc/testsuite/gcc.target/aarch64/acle/pr110100.c |  7 ++
 gcc/testsuite/gcc.target/aarch64/acle/pr110132.c | 15 ++++
 gcc/testsuite/gcc.target/powerpc/pr109932-1.c    | 17 +++++
 gcc/testsuite/gcc.target/powerpc/pr109932-2.c    | 17 +++++
 gcc/testsuite/gcc.target/powerpc/pr110011.c      | 42 +++++++++++
 gcc/testsuite/gcc.target/sparc/pr109541.c        | 23 ++++++
 gcc/testsuite/lib/target-supports.exp            |  2 +-
 libgo/Makefile.am                                |  1 +
 libgo/Makefile.in                                | 22 +++---
 libgo/go/runtime/mem_gccgo.go                    |  6 +-
 libgo/runtime/go-mmap.c                          | 21 ++++++
 libgo/runtime/runtime.h                          |  3 -
 30 files changed, 483 insertions(+), 113 deletions(-)

             reply	other threads:[~2023-06-22 13:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 13: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-09-08 11:19 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-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=20230622131905.27756385773F@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).