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-10977] Daily bump. Date: Fri, 9 Sep 2022 00:20:18 +0000 (GMT) [thread overview] Message-ID: <20220909002018.613C23858C2D@sourceware.org> (raw) https://gcc.gnu.org/g:106404001f9cfcddc681a90df9fc3f1cf116a665 commit r10-10977-g106404001f9cfcddc681a90df9fc3f1cf116a665 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Sep 9 00:19:41 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 7 +++++++ gcc/DATESTAMP | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index f6d64cd896e..7e2d8799b6d 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2022-09-08 Sebastian Huber <sebastian.huber@embedded-brains.de> + + * config/rs6000/rtems.h (CPP_OS_DEFAULT_SPEC): Define __PPC_VRSAVE__ if + -mvrsave is present. + * config/rs6000/t-rtems: Add -mvrsave multilib variants for + -mcpu=e6500. + 2022-08-30 Peter Bergner <bergner@linux.ibm.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 2e552cf7ab7..56639c30a8b 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220908 +20220909
reply other threads:[~2022-09-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=20220909002018.613C23858C2D@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).