public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/101751] asan_test.C fails with excess error with glibc-2.34 Date: Thu, 09 Dec 2021 18:28:57 +0000 [thread overview] Message-ID: <bug-101751-4-UgBxt4hMJB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101751 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>: https://gcc.gnu.org/g:9eeca99ccce4b56765920bd3c839abb77bbd4280 commit r12-5870-g9eeca99ccce4b56765920bd3c839abb77bbd4280 Author: Martin Sebor <msebor@redhat.com> Date: Thu Dec 9 11:24:14 2021 -0700 Avoid expecting nonzero size for access none void* arguments [PR101751]. Resolves: PR middle-end/101751 - attribute access none with void pointer expects nonzero size gcc/ChangeLog: PR middle-end/101751 * doc/extend.texi (attribute access): Adjust. * gimple-ssa-warn-access.cc (pass_waccess::maybe_check_access_sizes): Treat access mode none on a void* argument as expecting as few as zero bytes. gcc/testsuite/ChangeLog: PR middle-end/101751 * gcc.dg/Wstringop-overflow-86.c: New test.
next prev parent reply other threads:[~2021-12-09 18:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 12:43 [Bug testsuite/101751] New: " xry111 at mengyan1223 dot wang 2021-08-03 12:53 ` [Bug testsuite/101751] " fw at gcc dot gnu.org 2021-08-03 15:42 ` msebor at gcc dot gnu.org 2021-11-30 10:13 ` fw at gcc dot gnu.org 2021-12-09 18:28 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-12 0:08 ` xry111 at mengyan1223 dot wang 2021-12-16 23:04 ` cvs-commit at gcc dot gnu.org 2021-12-16 23:05 ` [Bug middle-end/101751] " msebor at gcc dot gnu.org
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=bug-101751-4-UgBxt4hMJB@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).