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 r12-8559] Daily bump.
Date: Sat,  9 Jul 2022 00:20:12 +0000 (GMT)	[thread overview]
Message-ID: <20220709002012.F009E385840C@sourceware.org> (raw)

https://gcc.gnu.org/g:3fbb94b3a4ac9fa35f0a3b1b5e69ab0d6924c5bf

commit r12-8559-g3fbb94b3a4ac9fa35f0a3b1b5e69ab0d6924c5bf
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Sat Jul 9 00:19:34 2022 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog           | 10 ++++++++++
 gcc/DATESTAMP           |  2 +-
 gcc/testsuite/ChangeLog |  7 +++++++
 3 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 7066a58ff76..e34775c433f 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2022-07-08  Lulu Cheng  <chenglulu@loongson.cn>
+
+	Backported from master:
+	2022-07-08  Lulu Cheng  <chenglulu@loongson.cn>
+
+	* config/loongarch/loongarch.cc (loongarch_compute_frame_info):
+	Modify fp_sp_offset and gp_sp_offset's calculation method,
+	when frame->mask or frame->fmask is zero, don't minus UNITS_PER_WORD
+	or UNITS_PER_FP_REG.
+
 2022-07-04  Andrew MacLeod  <amacleod@redhat.com>
 
 	PR tree-optimization/106114
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index aa8fe3c8911..2f349b0ec04 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220708
+20220709
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index d1f2cb7218a..9d106ff68ac 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,10 @@
+2022-07-08  Lulu Cheng  <chenglulu@loongson.cn>
+
+	Backported from master:
+	2022-07-08  Lulu Cheng  <chenglulu@loongson.cn>
+
+	* gcc.target/loongarch/prolog-opt.c: New test.
+
 2022-07-06  Jonathan Wakely  <jwakely@redhat.com>
 
 	Backported from master:


                 reply	other threads:[~2022-07-09  0:20 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=20220709002012.F009E385840C@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).