From 04a40f24cab0917c13dcd0467a5ffdac29413cf7 Mon Sep 17 00:00:00 2001 From: kazu Date: Mon, 21 Feb 2005 00:23:50 +0000 Subject: [PATCH] * gcse.c: Remove an obsolete comment. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@95318 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 4 ++++ gcc/gcse.c | 15 ++------------- 2 files changed, 6 insertions(+), 13 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 7ccb4af..33f411f 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2005-02-20 Kazu Hirata + + * gcse.c: Remove an obsolete comment. + 2005-02-20 Hans-Peter Nilsson * doc/extend.texi (Function Attributes) : The diff --git a/gcc/gcse.c b/gcc/gcse.c index 757f946..39a844f 100644 --- a/gcc/gcse.c +++ b/gcc/gcse.c @@ -264,19 +264,8 @@ Software Foundation, 59 Temple Place - Suite 330, Boston, MA the result of the expression is copied to a new register, and the redundant expression is deleted by replacing it with this new register. Classic GCSE doesn't have this problem as much as it computes the reaching defs of - each register in each block and thus can try to use an existing register. - - ********************** - - A fair bit of simplicity is created by creating small functions for simple - tasks, even when the function is only called in one place. This may - measurably slow things down [or may not] by creating more function call - overhead than is necessary. The source is laid out so that it's trivial - to make the affected functions inline so that one can measure what speed - up, if any, can be achieved, and maybe later when things settle things can - be rearranged. - - Help stamp out big monolithic functions! */ + each register in each block and thus can try to use an existing + register. */ /* GCSE global vars. */ -- 2.7.4