public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16447] out of ssa generates bloated code
Date: Wed, 06 Oct 2004 12:46:00 -0000	[thread overview]
Message-ID: <20041006124619.8009.qmail@sourceware.org> (raw)
In-Reply-To: <20040709032906.16447.dann@godzilla.ics.uci.edu>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-10-06 12:46 -------
Subject: Bug 16447

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	tree-cleanup-branch
Changes by:	amacleod@gcc.gnu.org	2004-10-06 12:46:04

Modified files:
	gcc            : ChangeLog tree-cfg.c tree-flow.h 
	                 tree-optimize.c tree-outof-ssa.c 

Log message:
	2004-10-06  Andrew MacLeod  <amacleod@redhat.com>
	
	PR tree-optimization/16447
	* tree-cfg.c (bsi_commit_one_edge_insert): Rename from
	bsi_commit_edge_inserts_1, and make funtion external.  Return new block.
	(bsi_commit_edge_inserts): Use renamed bsi_commit_one_edge_insert.
	* tree-optimize.c (pass_cleanup_cfg_post_optimizing): Enable listing.
	* tree-flow.h (bsi_commit_one_edge_insert): Extern decl.
	* tree-outof-ssa.c (rewrite_trees): Don't commit edges here.
	(same_stmt_list_p): New.  Return TRUE if edge is to be forwarded.
	(identical_copies_p): New.  Return true is two copies are the same.
	(identical_stmt_lists_p): New.  Return true if stmt lists are the same.
	(analyze_edges_for_bb): New.  Determine how best to insert edge stmts
	for a basic block.
	(perform_edge_inserts): New.  Determine what to do with all stmts that
	have been inserted on edges.
	(remove_ssa_form):  Analyze and commit edges from here.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=tree-cleanup-branch&r1=2.5512.2.2&r2=2.5512.2.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-cfg.c.diff?cvsroot=gcc&only_with_tag=tree-cleanup-branch&r1=2.55.2.3&r2=2.55.2.4
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-flow.h.diff?cvsroot=gcc&only_with_tag=tree-cleanup-branch&r1=2.46.2.2&r2=2.46.2.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-optimize.c.diff?cvsroot=gcc&only_with_tag=tree-cleanup-branch&r1=2.47.2.3&r2=2.47.2.4
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-outof-ssa.c.diff?cvsroot=gcc&only_with_tag=tree-cleanup-branch&r1=2.22.2.1&r2=2.22.2.2



-- 


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


  parent reply	other threads:[~2004-10-06 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09  3:29 [Bug tree-optimization/16447] New: " dann at godzilla dot ics dot uci dot edu
2004-07-09  3:30 ` [Bug tree-optimization/16447] " dann at godzilla dot ics dot uci dot edu
2004-07-09  3:57 ` pinskia at gcc dot gnu dot org
2004-07-09  4:02 ` pinskia at gcc dot gnu dot org
2004-09-28 20:12 ` pinskia at gcc dot gnu dot org
2004-09-29 20:21 ` amacleod at redhat dot com
2004-10-06 12:46 ` cvs-commit at gcc dot gnu dot org [this message]
2004-10-06 13:03 ` pinskia at gcc dot gnu dot org
2004-11-02  0:23 ` cvs-commit at gcc dot gnu dot org
2004-11-02  1:29 ` pinskia 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=20041006124619.8009.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).