public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "enkovich.gnu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/57055] New: Incorrect CFG after transactional memory passes
Date: Wed, 24 Apr 2013 12:22:00 -0000	[thread overview]
Message-ID: <bug-57055-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 57055
           Summary: Incorrect CFG after transactional memory passes
    Classification: Unclassified
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: enkovich.gnu@gmail.com


Transactional passes do not set cfun->calls_setjmp to true and do not fix CFG
accordingly after adding __builtin__ITM_beginTransaction call having
ECF_RETURNS_TWICE flag set.

It leads to inconsistency which may be revealed with special calls flags
recomputation.

If I add DCE pass after transactional memory then flags are recomputed and CFG
check fails because of call statements in the middle of basic block. Thus DCE
pass after transactional memory causes ~250 new fails in 'make check'.


Tried on 'gcc version 4.9.0 20130422 (experimental) (GCC)'


             reply	other threads:[~2013-04-24 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 12:22 enkovich.gnu at gmail dot com [this message]
2013-04-24 13:15 ` [Bug middle-end/57055] " jakub at gcc dot gnu.org
2013-04-25  8:17 ` rguenth 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-57055-4@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).