summaryrefslogtreecommitdiff
path: root/gcc/tree-ssa-loop-ivopts.c
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2019-01-12 17:55:45 +0100
committerJakub Jelinek <jakub@gcc.gnu.org>2019-01-12 17:55:45 +0100
commit5f07d78a1377dec492ae6a8829d1d68c32d8ef0f (patch)
tree20d0c685962437e8b368a71862f20f29b9131269 /gcc/tree-ssa-loop-ivopts.c
parentbbf18dc5d248a79a20ebf4b3a751669cd75485fd (diff)
tree-ssa-loop-ivopts.c (find_inv_vars): Fix a comment typo.
* tree-ssa-loop-ivopts.c (find_inv_vars): Fix a comment typo. * c-typeck.c (convert_for_assignment): Fix a comment typo. From-SVN: r267882
Diffstat (limited to 'gcc/tree-ssa-loop-ivopts.c')
-rw-r--r--gcc/tree-ssa-loop-ivopts.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/tree-ssa-loop-ivopts.c b/gcc/tree-ssa-loop-ivopts.c
index af0c9816bf7..a4cf64e3a13 100644
--- a/gcc/tree-ssa-loop-ivopts.c
+++ b/gcc/tree-ssa-loop-ivopts.c
@@ -3037,7 +3037,7 @@ find_inv_vars (struct ivopts_data *data, tree *expr_p, bitmap *inv_vars)
It's hard to make decision whether constant part should be stripped
or not. We choose to not strip based on below facts:
1) We need to count ADD cost for constant part if it's stripped,
- which is't always trivial where this functions is called.
+ which isn't always trivial where this functions is called.
2) Stripping constant away may be conflict with following loop
invariant hoisting pass.
3) Not stripping constant away results in more invariant exprs,