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/112709] [13 Regression] address sanitize and returns_twice causes an ICE
Date: Fri, 15 Mar 2024 23:29:55 +0000 [thread overview]
Message-ID: <bug-112709-4-TmihkTCBDC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112709-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112709
--- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:847391913443069358986b398c2f86dac906d742
commit r13-8454-g847391913443069358986b398c2f86dac906d742
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 13 09:19:05 2024 +0100
asan: Fix ICE during instrumentation of returns_twice calls [PR112709]
The following patch on top of the previously posted ubsan/gimple-iterator
one handles asan the same. While the case of returning by hidden reference
is handled differently because of the first recently posted asan patch,
this deals with instrumentation of the aggregates returned in registers
case as well as instrumentation of loads from aggregate memory in the
function arguments of returns_twice calls.
2024-03-13 Jakub Jelinek <jakub@redhat.com>
PR sanitizer/112709
* asan.cc (maybe_create_ssa_name, maybe_cast_to_ptrmode,
build_check_stmt, maybe_instrument_call, asan_expand_mark_ifn): Use
gsi_safe_insert_before instead of gsi_insert_before.
* gcc.dg/asan/pr112709-2.c: New test.
(cherry picked from commit 6586359e8e4c611dd96129b5d4f24023949ac3fc)
next prev parent reply other threads:[~2024-03-15 23:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 5:43 [Bug tree-optimization/112709] New: ICE verify_flow_info failed during GIMPLE pass: asan0 iamanonymous.cs at gmail dot com
2023-11-25 19:53 ` [Bug sanitizer/112709] [13/14 Regression] address sanitize and returns_twice causes an ICE pinskia at gcc dot gnu.org
2023-11-27 12:46 ` jakub at gcc dot gnu.org
2023-11-27 13:00 ` jakub at gcc dot gnu.org
2024-03-07 21:01 ` law at gcc dot gnu.org
2024-03-08 17:02 ` jakub at gcc dot gnu.org
2024-03-08 17:19 ` jakub at gcc dot gnu.org
2024-03-08 17:20 ` jakub at gcc dot gnu.org
2024-03-12 10:35 ` cvs-commit at gcc dot gnu.org
2024-03-12 13:22 ` jakub at gcc dot gnu.org
2024-03-13 8:18 ` cvs-commit at gcc dot gnu.org
2024-03-13 8:20 ` cvs-commit at gcc dot gnu.org
2024-03-15 14:15 ` [Bug sanitizer/112709] [13 " jakub at gcc dot gnu.org
2024-03-15 23:29 ` cvs-commit at gcc dot gnu.org
2024-03-15 23:29 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-18 14:42 ` jakub 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-112709-4-TmihkTCBDC@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: 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).