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 r9-9302] Daily bump. Date: Tue, 23 Mar 2021 00:19:22 +0000 (GMT) [thread overview] Message-ID: <20210323001922.E2A973858004@sourceware.org> (raw) https://gcc.gnu.org/g:0da207798f11dbedc925638911d7611ada65f11f commit r9-9302-g0da207798f11dbedc925638911d7611ada65f11f Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Mar 23 00:18:52 2021 +0000 Daily bump. Diff: --- gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 3f0cdc6c53e..19f595b3066 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2021-03-22 Kito Cheng <kito.cheng@sifive.com> + + Backported from master: + 2021-03-22 Kito Cheng <kito.cheng@sifive.com> + + PR target/99702 + * config/riscv/riscv.c (riscv_expand_block_move): Get RTL value + after type checking. + 2021-03-18 Sinan Lin <sinan@isrc.iscas.ac.cn> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index e5e2f23c9ec..c3b41601dee 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20210322 +20210323 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index b4e8a21d4f2..6c17669b127 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2021-03-22 Kito Cheng <kito.cheng@sifive.com> + + Backported from master: + 2021-03-22 Kito Cheng <kito.cheng@sifive.com> + + PR target/99702 + * gcc.target/riscv/pr99702.c: New. + 2021-03-20 Harald Anlauf <anlauf@gmx.de> Backported from master:
reply other threads:[~2021-03-23 0:19 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=20210323001922.E2A973858004@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: linkBe 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).