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-10470] Daily bump. Date: Tue, 17 Jan 2023 00:20:48 +0000 (GMT) [thread overview] Message-ID: <20230117002048.688EC3858D32@sourceware.org> (raw) https://gcc.gnu.org/g:9b8a78db29d31d0f8c72d8b8436040d9c8f06bb8 commit r11-10470-g9b8a78db29d31d0f8c72d8b8436040d9c8f06bb8 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Jan 17 00:20:09 2023 +0000 Daily bump. Diff: --- gcc/ChangeLog | 8 ++++++++ gcc/DATESTAMP | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index ced81f1f468..1df3c5b818c 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,11 @@ +2023-01-16 Alex Coplan <alex.coplan@arm.com> + + Backported from master: + 2022-12-01 Alex Coplan <alex.coplan@arm.com> + + * varasm.c (assemble_variable): Fix type confusion bug when + checking for ".vtable_map_vars" section. + 2023-01-11 Eric Botcazou <ebotcazou@adacore.com> PR tree-optimization/108199 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 748a3e00583..9081c2e74e5 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230116 +20230117
reply other threads:[~2023-01-17 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=20230117002048.688EC3858D32@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).