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 middle-end/107317] [10 Regression] ICE in emit_redzone_byte, at asan.cc:1508
Date: Wed, 03 May 2023 15:19:40 +0000 [thread overview]
Message-ID: <bug-107317-4-mGqCFLHOLN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107317-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107317
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:2525ad2b2aa0c2ddc64b091ba8a35c04c47e8723
commit r10-11344-g2525ad2b2aa0c2ddc64b091ba8a35c04c47e8723
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Nov 24 11:29:54 2022 +0100
asan: Fix up error recovery for too large frames [PR107317]
asan_emit_stack_protection and functions it calls have various asserts that
verify sanity of the stack protection instrumentation. But, that
verification can easily fail if we've diagnosed a frame offset overflow.
asan_emit_stack_protection just emits some extra code in the prologue,
if we've reported errors, we aren't producing assembly, so it doesn't
really matter if we don't include the protection code, compilation
is going to fail anyway.
2022-11-24 Jakub Jelinek <jakub@redhat.com>
PR middle-end/107317
* asan.c: Include diagnostic-core.h.
(asan_emit_stack_protection): Return NULL early if seen_error ().
* gcc.dg/asan/pr107317.c: New test.
(cherry picked from commit b6330a7685476fc30b8ae9bbf3fca1a9b0d4be95)
next prev parent reply other threads:[~2023-05-03 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 17:29 [Bug fortran/107317] New: [10/11/12/13 " gscfq@t-online.de
2022-10-20 8:41 ` [Bug fortran/107317] " marxin at gcc dot gnu.org
2022-10-20 9:15 ` rguenth at gcc dot gnu.org
2022-10-20 18:51 ` anlauf at gcc dot gnu.org
2022-10-20 20:05 ` tkoenig at gcc dot gnu.org
2022-10-22 8:36 ` tkoenig at gcc dot gnu.org
2022-11-23 12:48 ` jakub at gcc dot gnu.org
2022-11-23 12:51 ` jakub at gcc dot gnu.org
2022-11-23 16:52 ` [Bug middle-end/107317] " jakub at gcc dot gnu.org
2022-11-24 10:30 ` cvs-commit at gcc dot gnu.org
2022-11-24 10:31 ` [Bug middle-end/107317] [10/11/12 " jakub at gcc dot gnu.org
2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:57 ` [Bug middle-end/107317] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org
2023-05-03 9:30 ` [Bug middle-end/107317] [10 " jakub at gcc dot gnu.org
2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-04 7:21 ` 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-107317-4-mGqCFLHOLN@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).