aboutsummaryrefslogtreecommitdiff
path: root/gcc/gimple-loop-versioning.cc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2020-03-18 12:56:26 +0100
committerJakub Jelinek <jakub@redhat.com>2020-03-18 12:56:26 +0100
commitd5029d45940e8c12b425b4d1a23081b4155caa61 (patch)
treee04a027c2ab748c3ac851b7a6dcbadb4863a5c5f /gcc/gimple-loop-versioning.cc
parentd91480dee934478063fe5945b73ff3c108e40a91 (diff)
downloadgcc-d5029d45940e8c12b425b4d1a23081b4155caa61.zip
gcc-d5029d45940e8c12b425b4d1a23081b4155caa61.tar.gz
gcc-d5029d45940e8c12b425b4d1a23081b4155caa61.tar.bz2
Fix up duplicated duplicated words in comments
Another set of duplicated word fixes for things I've missed last time. These include e.g. *.cc files I forgot about, or duplicated words at the start or end of line. 2020-03-18 Jakub Jelinek <jakub@redhat.com> * asan.c (get_mem_refs_of_builtin_call): Fix up duplicated word issue in a comment. * config/arc/arc.c (frame_stack_add): Likewise. * gimple-loop-versioning.cc (loop_versioning::analyze_arbitrary_term): Likewise. * ipa-predicate.c (predicate::remap_after_inlining): Likewise. * tree-ssa-strlen.h (handle_printf_call): Likewise. * tree-ssa-strlen.c (is_strlen_related_p): Likewise. * optinfo-emit-json.cc (optrecord_json_writer::add_record): Likewise. analyzer/ * sm-malloc.cc (malloc_state_machine::on_stmt): Fix up duplicated word issue in a comment. * region-model.cc (region_model::make_region_for_unexpected_tree_code, region_model::delete_region_and_descendents): Likewise. * engine.cc (class exploded_cluster): Likewise. * diagnostic-manager.cc (class path_builder): Likewise. cp/ * constraint.cc (resolve_function_concept_check, subsumes_constraints, strictly_subsumes): Fix up duplicated word issue in a comment. * coroutines.cc (build_init_or_final_await, captures_temporary): Likewise. * logic.cc (dnf_size_r, cnf_size_r): Likewise. * pt.c (append_type_to_template_for_access_check): Likewise. d/ * expr.cc (ExprVisitor::visit (CatAssignExp *)): Fix up duplicated word issue in a comment. * d-target.cc (Target::FPTypeProperties<T>::max): Likewise. fortran/ * class.c (generate_finalization_wrapper): Fix up duplicated word issue in a comment. * trans-types.c (gfc_get_nodesc_array_type): Likewise.
Diffstat (limited to 'gcc/gimple-loop-versioning.cc')
-rw-r--r--gcc/gimple-loop-versioning.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/gimple-loop-versioning.cc b/gcc/gimple-loop-versioning.cc
index c424b3a..ff6c561 100644
--- a/gcc/gimple-loop-versioning.cc
+++ b/gcc/gimple-loop-versioning.cc
@@ -1070,7 +1070,7 @@ loop_versioning::analyze_arbitrary_term (address_info &address,
where nothing in the way "x" and "y" are set gives a hint as to
whether "i" iterates over the innermost dimension of the array.
- In these situations it seems reasonable to assume the the
+ In these situations it seems reasonable to assume the
programmer has nested the loops appropriately (although of course
there are examples like GEMM in which this assumption doesn't hold
for all accesses in the loop).