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 r9-9919] Daily bump.
Date: Thu, 20 Jan 2022 00:19:59 +0000 (GMT)	[thread overview]
Message-ID: <20220120001959.F26153858D35@sourceware.org> (raw)

https://gcc.gnu.org/g:1ffff833b56864beaeaaeee2bd2e8227da1fa6bc

commit r9-9919-g1ffff833b56864beaeaaeee2bd2e8227da1fa6bc
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Thu Jan 20 00:19:24 2022 +0000

    Daily bump.

Diff:
---
 contrib/ChangeLog      | 6 ++++++
 gcc/DATESTAMP          | 2 +-
 libsanitizer/ChangeLog | 9 +++++++++
 3 files changed, 16 insertions(+), 1 deletion(-)

diff --git a/contrib/ChangeLog b/contrib/ChangeLog
index 96ec8313721..5408afd9969 100644
--- a/contrib/ChangeLog
+++ b/contrib/ChangeLog
@@ -1,3 +1,9 @@
+2022-01-19  Martin Liska  <mliska@suse.cz>
+
+	* git-backport.py: Sync from master.
+	* git-commit-mklog.py: Likewise.
+	* git-fix-changelog.py: New file.
+
 2022-01-17  Martin Liska  <mliska@suse.cz>
 
 	Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 71126d3d29c..261c631b6a2 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220119
+20220120
diff --git a/libsanitizer/ChangeLog b/libsanitizer/ChangeLog
index a82ac090821..2de8b7c96f1 100644
--- a/libsanitizer/ChangeLog
+++ b/libsanitizer/ChangeLog
@@ -1,3 +1,12 @@
+2022-01-19  H.J. Lu  <hjl.tools@gmail.com>
+
+	Backported from master:
+	2022-01-12  H.J. Lu  <hjl.tools@gmail.com>
+
+	PR sanitizer/102911
+	* asan/asan_malloc_linux.cc (kDlsymAllocPoolSize): Set it to
+	8192 on Linux.
+
 2021-08-05  Martin Liska  <mliska@suse.cz>
 
 	PR sanitizer/101749


                 reply	other threads:[~2022-01-20  0:19 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=20220120001959.F26153858D35@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: link
Be 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).