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-10388] Daily bump. Date: Tue, 22 Nov 2022 00:21:01 +0000 (GMT) [thread overview] Message-ID: <20221122002101.BCC8A3852C47@sourceware.org> (raw) https://gcc.gnu.org/g:e90e34c721de1b27dda87d8af3678def8e99b6b8 commit r11-10388-ge90e34c721de1b27dda87d8af3678def8e99b6b8 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Nov 22 00:20:21 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 26 ++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ libatomic/ChangeLog | 9 +++++++++ 4 files changed, 44 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 4a2cf2c230f..cbb726f2664 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,29 @@ +2022-11-21 Jakub Jelinek <jakub@redhat.com> + + Backported from master: + 2022-11-21 Jakub Jelinek <jakub@redhat.com> + + PR target/107748 + * config/i386/smmintrin.h (_mm_extract_ps): Uglify names of local + variables and union members. + +2022-11-21 Jakub Jelinek <jakub@redhat.com> + + Backported from master: + 2022-11-20 Jakub Jelinek <jakub@redhat.com> + + PR target/107183 + * reg-stack.c (next_flags_user): Add DEBUG_SEEN argument. + If >= 0 and a DEBUG_INSN would be otherwise returned, set + DEBUG_SEEN to 1 and ignore it. + (swap_rtx_condition): Add DEBUG_SEEN argument. In >= 0 + mode only set DEBUG_SEEN to 1 if problematic DEBUG_ISNSs + were seen and revert all changes on success in that case. + Don't try to recog_memoized DEBUG_INSNs. + (compare_for_stack_reg): Adjust swap_rtx_condition caller. + If it returns true and debug_seen is 1, call swap_rtx_condition + again with debug_seen -1. + 2022-11-19 Thomas Schwinge <thomas@codesourcery.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index b4f44f494dc..00ec7aeeb71 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221121 +20221122 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index e894ec8f2c8..36f2e10fde5 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-11-21 Jakub Jelinek <jakub@redhat.com> + + Backported from master: + 2022-11-20 Jakub Jelinek <jakub@redhat.com> + + PR target/107183 + * gcc.dg/ubsan/pr107183.c: New test. + 2022-11-18 Marek Polacek <polacek@redhat.com> Backported from master: diff --git a/libatomic/ChangeLog b/libatomic/ChangeLog index ae629bf4079..22d4396db06 100644 --- a/libatomic/ChangeLog +++ b/libatomic/ChangeLog @@ -1,3 +1,12 @@ +2022-11-21 Jakub Jelinek <jakub@redhat.com> + + Backported from master: + 2022-11-15 Jakub Jelinek <jakub@redhat.com> + + PR target/104688 + * config/x86/init.c (__libat_feat1_init): Don't clear + bit_AVX on AMD CPUs. + 2022-04-21 Release Manager * GCC 11.3.0 released.
reply other threads:[~2022-11-22 0:21 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=20221122002101.BCC8A3852C47@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).