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-10393] Daily bump. Date: Fri, 25 Nov 2022 10:06:33 +0000 (GMT) [thread overview] Message-ID: <20221125100633.38393385B1AB@sourceware.org> (raw) https://gcc.gnu.org/g:9b66efb0c95846207f4ff8f197fc7a165760c511 commit r11-10393-g9b66efb0c95846207f4ff8f197fc7a165760c511 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Nov 25 10:05:53 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 9 +++++++++ 3 files changed, 19 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index cbb726f2664..80d9e220900 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2022-11-25 Eric Botcazou <ebotcazou@adacore.com> + + * range-op.cc (operator_bitwise_xor::op1_range): Fix thinko. + +2022-11-25 Eric Botcazou <ebotcazou@adacore.com> + + * tree-loop-distribution.c (loop_distribution::classify_builtin_ldst): + Bail out if source and destination do not have the same storage order. + 2022-11-21 Jakub Jelinek <jakub@redhat.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 059dd7f104c..9fb04058de4 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221124 +20221125 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 36f2e10fde5..3feb5ee1514 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,12 @@ +2022-11-25 Eric Botcazou <ebotcazou@adacore.com> + + * gnat.dg/opt100.adb: New test. + * gnat.dg/opt100_pkg.adb, gnat.dg/opt100_pkg.ads: New helper. + +2022-11-25 Eric Botcazou <ebotcazou@adacore.com> + + * gnat.dg/sso18.adb: New test. + 2022-11-21 Jakub Jelinek <jakub@redhat.com> Backported from master:
reply other threads:[~2022-11-25 10:06 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=20221125100633.38393385B1AB@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).