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-11008] Daily bump. Date: Thu, 29 Sep 2022 00:19:00 +0000 (GMT) [thread overview] Message-ID: <20220929001900.B3D883858D37@sourceware.org> (raw) https://gcc.gnu.org/g:4e80bbbf45352e5894fbebb7f33e984ada47aff4 commit r10-11008-g4e80bbbf45352e5894fbebb7f33e984ada47aff4 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Thu Sep 29 00:18:23 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 6 ++++++ gcc/DATESTAMP | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 846570b2d35..fabb51e5db5 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2022-09-28 Kyrylo Tkachov <kyrylo.tkachov@arm.com> + + * config/aarch64/aarch64-cores.def (neoverse-v2): New entry. + * config/aarch64/aarch64-tune.md: Regenerate. + * doc/invoke.texi (AArch64 Options): Document neoverse-v2. + 2022-09-21 Richard Sandiford <richard.sandiford@arm.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 8830fa8da31..ea4b4d1bd3b 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220928 +20220929
reply other threads:[~2022-09-29 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=20220929001900.B3D883858D37@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).