public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/39120] [4.2/4.3/4.4 Regression] Missed escape constraints for call results
Date: Tue, 24 Mar 2009 14:20:00 -0000 [thread overview]
Message-ID: <20090324142036.25340.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39120-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from rguenther at suse dot de 2009-03-24 14:20 -------
Subject: Re: [4.2/4.3/4.4 Regression] Missed
escape constraints for call results
On Tue, 24 Mar 2009, howarth at nitro dot med dot uc dot edu wrote:
> ------- Comment #3 from howarth at nitro dot med dot uc dot edu 2009-03-24 14:02 -------
> Can this be back ported to gcc trunk?
It can, but it would drag in some dependencies, in particular the CALLUSED
handling rewrite and eventually the changes related to handling NONLOCAL
vs. ESCAPED. I will try to cook up sth but planned to merge these changes
early in stage1 to backport them for 4.4.1 eventually.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39120
next prev parent reply other threads:[~2009-03-24 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 17:59 [Bug tree-optimization/39120] New: " rguenth at gcc dot gnu dot org
2009-02-06 17:59 ` [Bug tree-optimization/39120] " rguenth at gcc dot gnu dot org
2009-02-07 12:31 ` rguenth at gcc dot gnu dot org
2009-02-09 21:22 ` jsm28 at gcc dot gnu dot org
2009-03-24 14:03 ` howarth at nitro dot med dot uc dot edu
2009-03-24 14:20 ` rguenther at suse dot de [this message]
2009-03-24 14:40 ` rguenth at gcc dot gnu dot org
2009-03-24 14:40 ` rguenth at gcc dot gnu dot org
2009-03-27 22:37 ` rguenth at gcc dot gnu dot org
2009-03-27 22:41 ` rguenth at gcc dot gnu dot org
2009-03-31 21:12 ` [Bug tree-optimization/39120] [4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-06-17 12:40 ` rguenth at gcc dot gnu dot org
2009-08-04 12:51 ` rguenth at gcc dot gnu dot org
2010-05-22 18:31 ` rguenth at gcc dot gnu dot 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=20090324142036.25340.qmail@sourceware.org \
--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).