public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51212] ICE: verify_flow_info failed: BB 3 can not throw but has an EH edge with -fgnu-tm -fnon-call-exceptions and transaction_callable
Date: Wed, 21 Dec 2011 16:29:00 -0000	[thread overview]
Message-ID: <bug-51212-4-mnxGnWxhCr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51212-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51212

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot       |aldyh at gcc dot gnu.org
                   |gnu.org                     |

--- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> 2011-12-21 16:28:12 UTC ---
The problem here is that with -fnon-call-exceptions, the load from *p may trap,
but when we instrument the store, we have lost the landing pad information.

We can save and attach the exception information to the instrumented load
(_ITM_RU*), but currently all the TM load/store builtins are marked as
no-throw.  Perhaps we can get rid of the no-throw bit when
-fnon-call-exceptions is enabled.

Maybe something like this:

1. Get rid of the NOTHROW bits from the TM load/store builtins.
2. Attach the EH information to the TM load/store calls.
3. Split the BB accordingly when the TM load/store calls are not the last in
the BB (because we have added a cast after the instrumentation).

How does this sound Richard?


  parent reply	other threads:[~2011-12-21 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 18:12 [Bug middle-end/51212] New: " zsojka at seznam dot cz
2011-12-14  2:29 ` [Bug middle-end/51212] " pinskia at gcc dot gnu.org
2011-12-21 16:29 ` aldyh at gcc dot gnu.org [this message]
2011-12-21 17:26 ` rth at gcc dot gnu.org
2011-12-22 20:21 ` aldyh at gcc dot gnu.org
2011-12-22 20:43 ` aldyh at gcc dot gnu.org
2012-01-04 14:54 ` aldyh 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-51212-4-mnxGnWxhCr@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).