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-8873] Daily bump. Date: Fri, 28 Oct 2022 00:23:27 +0000 (GMT) [thread overview] Message-ID: <20221028002336.501BE385736B@sourceware.org> (raw) https://gcc.gnu.org/g:578e0131c220f4a568b1732397be7e85f13b9071 commit r12-8873-g578e0131c220f4a568b1732397be7e85f13b9071 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Oct 28 00:22:49 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 8 ++++++++ gcc/DATESTAMP | 2 +- gcc/lto/ChangeLog | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 24084056932..78f4cfa5e27 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,11 @@ +2022-10-27 Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> + + Backported from master: + 2022-10-27 Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> + Yvan ROUX <yvan.roux@foss.st.com> + + * ira.cc: Resize array after reg number increased. + 2022-10-26 Philipp Tomsich <philipp.tomsich@vrull.eu> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 494f34d4962..7109ae30352 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221027 +20221028 diff --git a/gcc/lto/ChangeLog b/gcc/lto/ChangeLog index 4805a59b044..639d861d399 100644 --- a/gcc/lto/ChangeLog +++ b/gcc/lto/ChangeLog @@ -1,3 +1,11 @@ +2022-10-27 Martin Liska <mliska@suse.cz> + + Backported from master: + 2022-10-27 Martin Liska <mliska@suse.cz> + + PR lto/107418 + * lto-dump.cc (lto_main): Do not load LTO stream for aliases. + 2022-08-19 Release Manager * GCC 12.2.0 released.
reply other threads:[~2022-10-28 0:23 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=20221028002336.501BE385736B@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).