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-10391] Daily bump.
Date: Wed, 24 Apr 2024 00:20:54 +0000 (GMT) [thread overview]
Message-ID: <20240424002054.59AB3385840D@sourceware.org> (raw)
https://gcc.gnu.org/g:dc95ed6c1e4551f47541959665d2179c44e98792
commit r12-10391-gdc95ed6c1e4551f47541959665d2179c44e98792
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Wed Apr 24 00:20:32 2024 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 37 +++++++++++++++++++++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 24 ++++++++++++++++++++++++
3 files changed, 62 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index f99a7953abe..dcdcf632ad3 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,40 @@
+2024-04-23 Jakub Jelinek <jakub@redhat.com>
+
+ Backported from master:
+ 2024-03-26 Jakub Jelinek <jakub@redhat.com>
+
+ PR sanitizer/111736
+ * tsan.cc (instrument_expr): Punt on non-generic address space
+ accesses.
+
+2024-04-23 Jakub Jelinek <jakub@redhat.com>
+
+ Backported from master:
+ 2024-03-22 Jakub Jelinek <jakub@redhat.com>
+
+ PR sanitizer/111736
+ * ubsan.cc (ubsan_expand_null_ifn, instrument_mem_ref): Avoid
+ SANITIZE_NULL instrumentation for non-generic address spaces
+ for which targetm.addr_space.zero_address_valid (as) is true.
+
+2024-04-23 Richard Biener <rguenther@suse.de>
+
+ Backported from master:
+ 2024-03-21 Richard Biener <rguenther@suse.de>
+
+ PR tree-optimization/111736
+ * asan.cc (instrument_derefs): Do not instrument accesses
+ to non-generic address-spaces.
+
+2024-04-23 Richard Biener <rguenther@suse.de>
+
+ Backported from master:
+ 2023-12-05 Richard Biener <rguenther@suse.de>
+
+ PR sanitizer/111736
+ * asan.cc (asan_protect_global): Do not protect globals
+ in non-generic address-space.
+
2024-04-22 Iain Sandoe <iain@sandoe.co.uk>
Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index f007dcf5a81..de7a64b42d7 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20240423
+20240424
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 8d843fe2342..f1abb29bf8e 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,27 @@
+2024-04-23 Jakub Jelinek <jakub@redhat.com>
+
+ Backported from master:
+ 2024-03-26 Jakub Jelinek <jakub@redhat.com>
+
+ PR sanitizer/111736
+ * gcc.dg/tsan/pr111736.c: New test.
+
+2024-04-23 Jakub Jelinek <jakub@redhat.com>
+
+ Backported from master:
+ 2024-03-22 Jakub Jelinek <jakub@redhat.com>
+
+ PR sanitizer/111736
+ * gcc.dg/ubsan/pr111736.c: New test.
+
+2024-04-23 Richard Biener <rguenther@suse.de>
+
+ Backported from master:
+ 2024-03-21 Richard Biener <rguenther@suse.de>
+
+ PR tree-optimization/111736
+ * gcc.target/i386/pr111736.c: New testcase.
+
2024-04-22 Iain Sandoe <iain@sandoe.co.uk>
Backported from master:
reply other threads:[~2024-04-24 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=20240424002054.59AB3385840D@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).