public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47530] [trans-mem] tail call optimization problem with _ITM_commitTransaction
Date: Wed, 09 Feb 2011 18:03:00 -0000 [thread overview]
Message-ID: <bug-47530-4-biZwAoAVLz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47530-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47530
Richard Henderson <rth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.02.09 17:36:18
AssignedTo|unassigned at gcc dot |rth at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #1 from Richard Henderson <rth at gcc dot gnu.org> 2011-02-09 17:36:18 UTC ---
Mine.
We aren't representing these functions as setjmp because we have more
detailed information about the control flow, and it's (eventually)
explicitly represented. For instance, if a function has two transactions
we know that the commit for the second transaction cannot branch to the
restart of the first transaction.
The problem here is that these extra edges are not inserted until after
the tail-call discovery pass is run. Thankfully, no actual transform
is actually performed at that spot. All we have to do later is clear
the bit that the tail-call discovery pass set.
next prev parent reply other threads:[~2011-02-09 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 11:24 [Bug c/47530] New: " patrick.marlier at gmail dot com
2011-02-09 18:03 ` rth at gcc dot gnu.org [this message]
2011-02-09 20:24 ` [Bug c/47530] " rth at gcc dot gnu.org
2011-02-09 20:30 ` rth at gcc dot gnu.org
2011-02-10 9:55 ` patrick.marlier at gmail dot com
2012-05-02 16:51 ` luked at cs dot rochester.edu
2012-05-02 16:53 ` luked at cs dot rochester.edu
2012-06-04 15:22 ` aldyh at gcc dot gnu.org
2012-06-04 15:25 ` aldyh at gcc dot gnu.org
2012-06-04 15:27 ` patrick.marlier at gmail dot com
2012-06-04 15:52 ` [Bug middle-end/47530] " aldyh at gcc dot gnu.org
2012-06-04 15:59 ` patrick.marlier at gmail dot com
2012-06-04 16:52 ` aldyh at gcc dot gnu.org
2012-06-04 16:53 ` aldyh at gcc dot gnu.org
2012-06-04 16:57 ` 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-47530-4-biZwAoAVLz@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).