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/104449] [9/10/11 Regression] ICE: verify_gimple failed: dead statement in EH table with -fexceptions -fsanitize=address -fstack-check=generic
Date: Sat, 19 Feb 2022 08:02:57 +0000 [thread overview]
Message-ID: <bug-104449-4-cAQjNPUqdy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104449-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104449
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:8a97d7bdb38285a7954f67172013098b61548870
commit r11-9604-g8a97d7bdb38285a7954f67172013098b61548870
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sat Feb 12 19:17:44 2022 +0100
asan: Fix up address sanitizer instrumentation of __builtin_alloca* if it
can throw [PR104449]
With -fstack-check* __builtin_alloca* can throw and the asan
instrumentation of this builtin wasn't prepared for that case.
The following patch fixes that by replacing the builtin with the
replacement builtin and emitting any further insns on the fallthru
edge.
I haven't touched the hwasan code which most likely suffers from the
same problem.
2022-02-12 Jakub Jelinek <jakub@redhat.com>
PR sanitizer/104449
* asan.c: Include tree-eh.h.
(handle_builtin_alloca): Handle the case when __builtin_alloca or
__builtin_alloca_with_align can throw.
* gcc.dg/asan/pr104449.c: New test.
* g++.dg/asan/pr104449.C: New test.
(cherry picked from commit f0c7367b8802c47efaad87b1f2126fe6350d8b47)
next prev parent reply other threads:[~2022-02-19 8:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:57 [Bug middle-end/104449] New: [9/10/11/12 " zsojka at seznam dot cz
2022-02-08 21:19 ` [Bug middle-end/104449] " pinskia at gcc dot gnu.org
2022-02-09 7:38 ` rguenth at gcc dot gnu.org
2022-02-10 16:27 ` jakub at gcc dot gnu.org
2022-02-11 14:46 ` jakub at gcc dot gnu.org
2022-02-11 18:31 ` [Bug sanitizer/104449] " jakub at gcc dot gnu.org
2022-02-12 12:20 ` ebotcazou at gcc dot gnu.org
2022-02-12 18:18 ` cvs-commit at gcc dot gnu.org
2022-02-12 18:21 ` [Bug sanitizer/104449] [9/10/11 " jakub at gcc dot gnu.org
2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-19 8:08 ` [Bug sanitizer/104449] [9/10 " jakub at gcc dot gnu.org
2022-04-12 7:21 ` jakub at gcc dot gnu.org
2022-05-10 8:23 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:24 ` cvs-commit at gcc dot gnu.org
2022-05-11 6:36 ` 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-104449-4-cAQjNPUqdy@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).