public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/104449] [9/10/11/12 Regression] ICE: verify_gimple failed: dead statement in EH table with -fexceptions -fsanitize=address -fstack-check=generic
Date: Sat, 12 Feb 2022 12:20:53 +0000 [thread overview]
Message-ID: <bug-104449-4-1dosH5w9xf@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
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu.org
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Confirmed. With -fstack-check=generic, __builtin_alloca_with_align is marked
> as being able to throw but asan decides to insert its annonations right
> after the builtin call instead of on the branch after the function call.
With any -fstack-check option to be exact:
/* If we're checking the stack, `alloca' can throw. */
const int alloca_flags
= ECF_MALLOC | ECF_LEAF | (flag_stack_check ? 0 : ECF_NOTHROW);
next prev parent reply other threads:[~2022-02-12 12:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:57 [Bug middle-end/104449] New: " 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 [this message]
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
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-1dosH5w9xf@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).