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-10337] Daily bump. Date: Wed, 26 Oct 2022 00:20:44 +0000 (GMT) [thread overview] Message-ID: <20221026002044.B153A3857406@sourceware.org> (raw) https://gcc.gnu.org/g:f747b2ca817184add50953a52efcb77146904010 commit r11-10337-gf747b2ca817184add50953a52efcb77146904010 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Oct 26 00:20:05 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 29 +++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 10 ++++++++++ 3 files changed, 40 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index a036ead0833..ec7069c4be3 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,32 @@ +2022-10-25 Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> + + Backported from master: + 2022-10-19 Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> + + PR target/106355 + * config/s390/s390.c (s390_call_saved_register_used): For a + parameter with BLKmode fix determining number of consecutive + registers. + +2022-10-25 Martin Liska <mliska@suse.cz> + + Backported from master: + 2022-10-25 Martin Liska <mliska@suse.cz> + + PR target/107364 + * common/config/i386/i386-cpuinfo.h (enum processor_vendor): + Fix pedantic warning. + +2022-10-25 Martin Liska <mliska@suse.cz> + + Backported from master: + 2022-10-24 Martin Liska <mliska@suse.cz> + + PR target/107364 + * common/config/i386/i386-cpuinfo.h (enum processor_vendor): + Reorder enum values as BUILTIN_VENDOR_MAX should not point + in the middle of the valid enum values. + 2022-10-20 Richard Sandiford <richard.sandiford@arm.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index c75820ce08e..03e9228fa2a 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221025 +20221026 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index ad1cd37630e..7eefa76299d 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,13 @@ +2022-10-25 Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> + + Backported from master: + 2022-10-19 Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> + + * gcc.target/s390/pr106355.h: Common code for new tests. + * gcc.target/s390/pr106355-1.c: New test. + * gcc.target/s390/pr106355-2.c: New test. + * gcc.target/s390/pr106355-3.c: New test. + 2022-10-24 Marek Polacek <polacek@redhat.com> Backported from master:
reply other threads:[~2022-10-26 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=20221026002044.B153A3857406@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).