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 r12-8894] Daily bump. Date: Sun, 6 Nov 2022 11:09:53 +0000 (GMT) [thread overview] Message-ID: <20221106111000.F2A313858C50@sourceware.org> (raw) https://gcc.gnu.org/g:64f22c4ee39f75c08e3c6585f23a9f5092da1c4c commit r12-8894-g64f22c4ee39f75c08e3c6585f23a9f5092da1c4c Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Nov 6 11:09:16 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 15 +++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 6 ++++++ 3 files changed, 22 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 197fa081cf3..4caf735f460 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,18 @@ +2022-11-05 Jonathan Wakely <jwakely@redhat.com> + + Backported from master: + 2022-11-05 Jonathan Wakely <jwakely@redhat.com> + + PR c/41041 + * doc/cppopts.texi: Document -fwide-exec-charset defaults + correctly. + +2022-11-04 Eric Botcazou <ebotcazou@adacore.com> + + * fold-const.cc (operand_compare::operand_equal_p) <COMPONENT_REF>: + Do not take into account operand 2. + (operand_compare::hash_operand) <COMPONENT_REF>: Likewise. + 2022-11-03 Uros Bizjak <ubizjak@gmail.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index c96f2246e01..a9017fbbe6b 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221104 +20221106 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 674b98d053d..f40f824c3c6 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,9 @@ +2022-11-04 Eric Botcazou <ebotcazou@adacore.com> + + * gnat.dg/opt99.adb: New test. + * gnat.dg/opt99_pkg1.ads, gnat.dg/opt99_pkg1.adb: New helper. + * gnat.dg/opt99_pkg2.ads: Likewise. + 2022-11-03 Uros Bizjak <ubizjak@gmail.com> Backported from master:
reply other threads:[~2022-11-06 11:09 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=20221106111000.F2A313858C50@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).