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 r10-10259] Daily bump. Date: Tue, 9 Nov 2021 00:17:58 +0000 (GMT) [thread overview] Message-ID: <20211109001758.BC5EE3858C2C@sourceware.org> (raw) https://gcc.gnu.org/g:91a66770873d51f31346de3e173ee7a8b3f6e86a commit r10-10259-g91a66770873d51f31346de3e173ee7a8b3f6e86a Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Nov 9 00:17:23 2021 +0000 Daily bump. Diff: --- contrib/ChangeLog | 9 +++++++++ gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- 3 files changed, 19 insertions(+), 1 deletion(-) diff --git a/contrib/ChangeLog b/contrib/ChangeLog index ac262eae462..da635e2e5fb 100644 --- a/contrib/ChangeLog +++ b/contrib/ChangeLog @@ -1,3 +1,12 @@ +2021-11-08 Martin Liska <mliska@suse.cz> + + * gcc-changelog/git_check_commit.py: Sync from master. + * gcc-changelog/git_commit.py: Likewise. + * gcc-changelog/git_email.py: Likewise. + * gcc-changelog/git_update_version.py: Likewise. + * gcc-changelog/test_email.py: Likewise. + * gcc-changelog/test_patches.txt: Likewise. + 2021-06-23 Martin Liska <mliska@suse.cz> * mklog.py: New file. diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 4c71d8dae1e..fc408c537f9 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2021-11-08 Kewen Lin <linkw@linux.ibm.com> + + Backported from master: + 2021-10-26 Kewen Lin <linkw@linux.ibm.com> + + PR tree-optimization/102789 + * tree-vect-loop-manip.c (vect_update_inits_of_drs): Do not + update inits of simd_lane_access. + 2021-11-03 Vladimir N. Makarov <vmakarov@redhat.com> PR rtl-optimization/102842 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index ead5f96b652..f11a2f562bb 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20211108 +20211109
reply other threads:[~2021-11-09 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=20211109001758.BC5EE3858C2C@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).