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-8617] Daily bump.
Date: Thu, 18 Apr 2024 00:21:16 +0000 (GMT)	[thread overview]
Message-ID: <20240418002117.705963858D20@sourceware.org> (raw)

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

commit r13-8617-gafbf411b311872a8221d3bc464142bfbc277349d
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Thu Apr 18 00:20:54 2024 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog | 24 ++++++++++++++++++++++++
 gcc/DATESTAMP |  2 +-
 2 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 5e50e9193ac..4f9f60eaad3 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,27 @@
+2024-04-17  Georg-Johann Lay  <avr@gjlay.de>
+
+	Backported from master:
+	2024-04-17  Georg-Johann Lay  <avr@gjlay.de>
+
+	PR target/114752
+	* config/avr/avr.cc (avr_print_operand) [CONST_DOUBLE_P]: Handle DFmode.
+
+2024-04-17  Sebastian Huber  <sebastian.huber@embedded-brains.de>
+
+	Backported from master:
+	2024-04-09  Sebastian Huber  <sebastian.huber@embedded-brains.de>
+
+	* config/rs6000/rtems.h (OS_MISSING_POWERPC64): Define.
+
+2024-04-17  Sebastian Huber  <sebastian.huber@embedded-brains.de>
+
+	Backported from master:
+	2024-04-09  Sebastian Huber  <sebastian.huber@embedded-brains.de>
+
+	* config.gcc (aarch64-*-rtems*): Add target makefile fragment
+	t-aarch64-rtems.
+	* config/aarch64/t-aarch64-rtems: New file.
+
 2024-04-15  Georg-Johann Lay  <avr@gjlay.de>
 
 	Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 02796385530..ee86d6c39bf 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20240417
+20240418

                 reply	other threads:[~2024-04-18  0:21 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=20240418002117.705963858D20@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).