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 r11-9648] Daily bump. Date: Fri, 11 Mar 2022 00:19:04 +0000 (GMT) [thread overview] Message-ID: <20220311001904.A9A083858D39@sourceware.org> (raw) https://gcc.gnu.org/g:2f79dccf6b816e23296ec43bc093485fd77f23f1 commit r11-9648-g2f79dccf6b816e23296ec43bc093485fd77f23f1 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Mar 11 00:18:24 2022 +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 7ae1c0cf74b..2a942cf8de7 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2022-03-10 Marek Polacek <polacek@redhat.com> + + Backported from master: + 2022-03-08 Marek Polacek <polacek@redhat.com> + + PR rtl-optimization/104777 + * rtl.c (classify_insn): For ASM_OPERANDS, return JUMP_INSN only if + ASM_OPERANDS_LABEL_VEC has at least one element. + 2022-03-09 Kito Cheng <kito.cheng@sifive.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 284de79460a..95bd2a4a3e0 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220310 +20220311 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 4b5997c1721..102d8290d51 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-03-10 Marek Polacek <polacek@redhat.com> + + Backported from master: + 2022-03-08 Marek Polacek <polacek@redhat.com> + + PR rtl-optimization/104777 + * gcc.dg/torture/tls/pr104777.c: New test. + 2022-03-09 Richard Biener <rguenther@suse.de> Backported from master:
reply other threads:[~2022-03-11 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=20220311001904.A9A083858D39@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).