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 sanitizer/97696] ICE since ASAN_MARK does not handle poly_int sized varibales Date: Wed, 27 Mar 2024 17:38:19 +0000 [thread overview] Message-ID: <bug-97696-4-4D4HY0kUU1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97696-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97696 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:51e1629bc11f0ae4b8050712b26521036ed360aa commit r12-10296-g51e1629bc11f0ae4b8050712b26521036ed360aa Author: Richard Sandiford <richard.sandiford@arm.com> Date: Wed Mar 27 17:38:09 2024 +0000 asan: Handle poly-int sizes in ASAN_MARK [PR97696] This patch makes the expansion of IFN_ASAN_MARK let through poly-int-sized objects. The expansion itself was already generic enough, but the tests for the fast path were too strict. gcc/ PR sanitizer/97696 * asan.cc (asan_expand_mark_ifn): Allow the length to be a poly_int. gcc/testsuite/ PR sanitizer/97696 * gcc.target/aarch64/sve/pr97696.c: New test. (cherry picked from commit fca6f6fddb22b8665e840f455a7d0318d4575227)
next prev parent reply other threads:[~2024-03-27 17:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-03 12:37 [Bug sanitizer/97696] New: " matmal01 at gcc dot gnu.org 2020-11-03 12:39 ` [Bug sanitizer/97696] " matmal01 at gcc dot gnu.org 2020-11-04 9:44 ` marxin at gcc dot gnu.org 2024-01-29 19:07 ` rvmallad at amazon dot com 2024-02-24 12:21 ` rsandifo at gcc dot gnu.org 2024-02-24 12:23 ` rsandifo at gcc dot gnu.org 2024-03-05 19:48 ` cvs-commit at gcc dot gnu.org 2024-03-06 1:52 ` rvmallad at amazon dot com 2024-03-27 15:30 ` cvs-commit at gcc dot gnu.org 2024-03-27 17:38 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-27 19:27 ` cvs-commit at gcc dot gnu.org 2024-03-27 19:28 ` rsandifo at gcc dot gnu.org 2024-03-27 19:30 ` pinskia 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-97696-4-4D4HY0kUU1@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).