procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

tree-ssa-loop-ivopts.c: Fix a comment typo.

Browse source 
* tree-ssa-loop-ivopts.c: Fix a comment typo.
	* doc/invoke.texi: Fix a typo.

From-SVN: r89759
This commit is contained in:
Kazu Hirata 2004-10-28 14:24:29 +00:00 • committed by Kazu Hirata
parent f340a501f7
commit 1c170b5eba
3 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/ChangeLog
View file

@ -1,3 +1,8 @@
2004-10-28 Kazu Hirata <kazu@cs.umass.edu>
* tree-ssa-loop-ivopts.c: Fix a comment typo.
* doc/invoke.texi: Fix a typo.
2004-10-28 Kazu Hirata <kazu@cs.umass.edu>
* Makefile.in (OBJS-common): Remove duplicates.

2
gcc/doc/invoke.texi
View file

@ -5322,7 +5322,7 @@ default value, 0, implies that GCC will select the most appropriate
size itself.
@item sra-field-structure-ratio
The treshold ratio (as a percentage) between instantiated fields and
The threshold ratio (as a percentage) between instantiated fields and
the complete structure size. We say that if the ratio of the number
of bytes in instantiated fields to the number of bytes in the complete
structure exceeds this parameter, then block copies are not used. The

2
gcc/tree-ssa-loop-ivopts.c
View file

@ -3615,7 +3615,7 @@ try_add_cand_for (struct ivopts_data *data, bitmap ivs, bitmap inv,
just one generic biv. If we added here many ivs specific to the uses,
the optimization algorithm later would be likely to get stuck in a local
minimum, thus causing us to create too many ivs. The approach from
few ivs to more seems more likely to be succesful -- starting from few
few ivs to more seems more likely to be successful -- starting from few
ivs, replacing an expensive use by a specific iv should always be a
win. */
EXECUTE_IF_SET_IN_BITMAP (data->important_candidates, 0, i, bi)