* gcse.c: Remove an obsolete comment.
From-SVN: r95318
This commit is contained in:
parent
f1cc922096
commit
a3c28ba275
@ -1,3 +1,7 @@
|
||||
2005-02-20 Kazu Hirata <kazu@cs.umass.edu>
|
||||
|
||||
* gcse.c: Remove an obsolete comment.
|
||||
|
||||
2005-02-20 Hans-Peter Nilsson <hp@axis.com>
|
||||
|
||||
* doc/extend.texi (Function Attributes) <Attribute const>: The
|
||||
|
15
gcc/gcse.c
15
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. */
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user