public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ctice at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59507] ICE: in mark_reachable_handlers, at tree-eh.c:3833 with -O -fnon-call-exceptions -fvtable-verify=preinit
Date: Tue, 22 Apr 2014 21:17:00 -0000 [thread overview]
Message-ID: <bug-59507-4-stSlphqs21@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59507-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59507
ctice at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ctice at gcc dot gnu.org
--- Comment #3 from ctice at gcc dot gnu.org ---
This is caused by the verification call being inserted after an exception
handler landing pad, in the same basic block as the landing pad, when GCC
expects the landing pad statement to be the last statement in the basic block.
The fix for this will be to split all the outgoing edges and insert new basic
blocks on each, with the verification call in there instead. I will work on
this, but it may take me a little time to get right.
next prev parent reply other threads:[~2014-04-22 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 13:17 [Bug middle-end/59507] New: " zsojka at seznam dot cz
2013-12-14 13:23 ` [Bug middle-end/59507] " mpolacek at gcc dot gnu.org
2014-04-22 11:37 ` jakub at gcc dot gnu.org
2014-04-22 21:17 ` ctice at gcc dot gnu.org [this message]
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-10-30 10:42 ` jakub at gcc dot gnu.org
2015-06-26 19:57 ` jakub at gcc dot gnu.org
2015-06-26 20:28 ` jakub at gcc dot gnu.org
2021-08-08 16:29 ` pinskia at gcc dot gnu.org
2021-08-08 16:31 ` 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-59507-4-stSlphqs21@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).