public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23940] SSA_NAMEs are not released after no longer being used.
Date: Mon, 19 Sep 2005 16:05:00 -0000 [thread overview]
Message-ID: <20050919160510.21618.qmail@sourceware.org> (raw)
In-Reply-To: <20050918005013.23940.pinskia@gcc.gnu.org>
------- Additional Comments From pinskia at physics dot uc dot edu 2005-09-19 16:05 -------
Subject: Re: SSA_NAMEs are not released after no longer being used.
On Sep 19, 2005, at 11:59 AM, amacleod at redhat dot com wrote:
> We also probably have to set SSA_NAME_DEF_STMT to NULL in bsi_remove
> in order to
> be sure that an SSA name with no uses isn't actually associated with a
> stmt any
> more (you can have valid defs with no uses). It is set when the
> SSA_NAME is
> created, but I don't think that field ever gets cleared anywhere else.
Except that does not work as mentioned before as people do bsi_remove
and then bsi_insert on the same staement when moving the statement
around.
And isn't that the same thing as adding release_defs in bsi_remove?
And that will not work for the SSA_NAMEs used for aliasing and then the
variable becomes a gimple register.
-- Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23940
next prev parent reply other threads:[~2005-09-19 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 0:50 [Bug tree-optimization/23940] New: " pinskia at gcc dot gnu dot org
2005-09-19 14:03 ` [Bug tree-optimization/23940] " amacleod at redhat dot com
2005-09-19 15:24 ` pinskia at gcc dot gnu dot org
2005-09-19 15:45 ` amacleod at redhat dot com
2005-09-19 15:50 ` pinskia at gcc dot gnu dot org
2005-09-19 15:59 ` amacleod at redhat dot com
2005-09-19 16:05 ` pinskia at physics dot uc dot edu [this message]
2005-09-19 16:33 ` amacleod at redhat dot com
2005-09-19 16:44 ` pinskia at physics dot uc dot edu
2005-09-19 18:10 ` amacleod at redhat dot com
2005-09-19 20:34 ` amacleod at redhat dot com
2005-09-30 14:58 ` amacleod at redhat dot com
[not found] <bug-23940-6528@http.gcc.gnu.org/bugzilla/>
2005-10-15 16:38 ` pinskia at gcc dot gnu dot org
2006-12-20 21:44 ` jimbob at google dot com
2008-07-15 12:39 ` rguenth at gcc dot gnu dot org
2009-02-22 14:23 ` steven at gcc dot gnu dot org
2009-02-22 19:06 ` rguenth at gcc dot gnu dot org
2009-04-03 10:29 ` rguenth at gcc dot gnu dot org
2009-04-03 10:29 ` 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=20050919160510.21618.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).