public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6352] Daily bump.
Date: Mon, 27 Feb 2023 00:17:12 +0000 (GMT)	[thread overview]
Message-ID: <20230227001713.21C2D3858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:2cd665b1a939c97fbf053d998cf687943bc07e47

commit r13-6352-g2cd665b1a939c97fbf053d998cf687943bc07e47
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Mon Feb 27 00:16:28 2023 +0000

    Daily bump.

Diff:
---
 gcc/DATESTAMP           | 2 +-
 gcc/ada/ChangeLog       | 6 ++++++
 gcc/testsuite/ChangeLog | 4 ++++
 3 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 6ee65af5879..89de5893b85 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20230226
+20230227
diff --git a/gcc/ada/ChangeLog b/gcc/ada/ChangeLog
index fdbbf4cc4ee..f0113f0855d 100644
--- a/gcc/ada/ChangeLog
+++ b/gcc/ada/ChangeLog
@@ -1,3 +1,9 @@
+2023-02-26  Peter Foley  <pefoley2@pefoley.com>
+
+	PR ada/108909
+	* Make-generated.in: Use GNATMAKE.
+	* gcc-interface/Makefile.in: Ditto.
+
 2023-02-14  Eric Botcazou  <ebotcazou@adacore.com>
 
 	* gcc-interface/trans.cc (gnat_gimplify_expr): Add missing guard.
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index af15c6c969f..ec47d35064b 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2023-02-26  Eric Botcazou  <ebotcazou@adacore.com>
+
+	* ada/acats/run_all.sh: Adjust example of compiler options.
+
 2023-02-25  Gaius Mulley  <gaiusmod2@gmail.com>
 
 	* gm2/projects/pim/run/pass/tower/projects-pim-run-pass-tower.exp:

                 reply	other threads:[~2023-02-27  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230227001713.21C2D3858D32@sourceware.org \
    --to=gccadmin@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).