From c46b5b0a2c10139379a25b0071aa8997af41220d Mon Sep 17 00:00:00 2001 From: Jakub Jelinek Date: Thu, 23 Mar 2023 15:25:50 +0100 Subject: ranger: Ranger meets aspell I've noticed a comment typo in tree-vrp.cc and decided to quickly skim aspell -c on the ranger sources (with quick I on everything that looked ok or roughly ok). But not being a native English speaker, I could get stuff wrong. 2023-03-23 Jakub Jelinek * value-range.cc (irange::irange_union, irange::intersect): Fix comment spelling bugs. * gimple-range-trace.cc (range_tracer::do_header): Likewise. * gimple-range-trace.h: Likewise. * gimple-range-edge.cc: Likewise. (gimple_outgoing_range_stmt_p, gimple_outgoing_range::switch_edge_range, gimple_outgoing_range::edge_range_p): Likewise. * gimple-range.cc (gimple_ranger::prefill_stmt_dependencies, gimple_ranger::fold_stmt, gimple_ranger::register_transitive_infer, assume_query::assume_query, assume_query::calculate_phi): Likewise. * gimple-range-edge.h: Likewise. * value-range.h (Value_Range::set, Value_Range::lower_bound, Value_Range::upper_bound, frange::set_undefined): Likewise. * gimple-range-gori.h (range_def_chain::depend, gori_map::m_outgoing, gori_compute): Likewise. * gimple-range-fold.h (fold_using_range): Likewise. * gimple-range-path.cc (path_range_query::compute_ranges_in_phis): Likewise. * gimple-range-gori.cc (range_def_chain::in_chain_p, range_def_chain::dump, gori_map::calculate_gori, gori_compute::compute_operand_range_switch, gori_compute::logical_combine, gori_compute::refine_using_relation, gori_compute::compute_operand1_range, gori_compute::may_recompute_p): Likewise. * gimple-range.h: Likewise. (enable_ranger): Likewise. * range-op.h (empty_range_varying): Likewise. * value-query.h (value_query): Likewise. * gimple-range-cache.cc (block_range_cache::set_bb_range, block_range_cache::dump, ssa_global_cache::clear_global_range, temporal_cache::temporal_value, temporal_cache::current_p, ranger_cache::range_of_def, ranger_cache::propagate_updated_value, ranger_cache::range_from_dom, ranger_cache::register_inferred_value): Likewise. * gimple-range-fold.cc (fur_edge::get_phi_operand, fur_stmt::get_operand, gimple_range_adjustment, fold_using_range::range_of_phi, fold_using_range::relation_fold_and_or): Likewise. * value-range-storage.h (irange_storage_slot::MAX_INTS): Likewise. * value-query.cc (range_query::value_of_expr, range_query::value_on_edge, range_query::query_relation): Likewise. * tree-vrp.cc (remove_unreachable::remove_and_update_globals, intersect_range_with_nonzero_bits): Likewise. * gimple-range-infer.cc (gimple_infer_range::check_assume_func, exit_range): Likewise. * value-relation.h: Likewise. (equiv_oracle, relation_trio::relation_trio, value_relation, value_relation::value_relation, pe_min): Likewise. * range-op-float.cc (range_operator_float::rv_fold, frange_arithmetic, foperator_unordered_equal::op1_range, foperator_div::rv_fold): Likewise. * gimple-range-op.cc (cfn_clz::fold_range): Likewise. * value-relation.cc (equiv_oracle::query_relation, equiv_oracle::register_equiv, equiv_oracle::add_equiv_to_block, value_relation::apply_transitive, relation_chain_head::find_relation, dom_oracle::query_relation, dom_oracle::find_relation_block, dom_oracle::find_relation_dom, path_oracle::register_equiv): Likewise. * range-op.cc (range_operator::wi_fold_in_parts_equiv, create_possibly_reversed_range, adjust_op1_for_overflow, operator_mult::wi_fold, operator_exact_divide::op1_range, operator_cast::lhs_op1_relation, operator_cast::fold_pair, operator_cast::fold_range, operator_abs::wi_fold, range_op_cast_tests, range_op_lshift_tests): Likewise. --- gcc/range-op-float.cc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'gcc/range-op-float.cc') diff --git a/gcc/range-op-float.cc b/gcc/range-op-float.cc index 204b391..9564114 100644 --- a/gcc/range-op-float.cc +++ b/gcc/range-op-float.cc @@ -117,7 +117,7 @@ range_operator_float::fold_range (frange &r, tree type, // For a given operation, fold two sets of ranges into [lb, ub]. // MAYBE_NAN is set to TRUE if, in addition to any result in LB or -// UB, the final range has the possiblity of a NAN. +// UB, the final range has the possibility of a NAN. void range_operator_float::rv_fold (REAL_VALUE_TYPE &lb, REAL_VALUE_TYPE &ub, @@ -299,9 +299,9 @@ frange_nextafter (enum machine_mode mode, // -fexcess-precision=standard we perform most SF/DFmode arithmetic in // XFmode (long_double_type_node), so that case is OK. But without // -mfpmath=sse, all the SF/DFmode computations are in XFmode -// precision (64-bit mantissa) and only occassionally rounded to +// precision (64-bit mantissa) and only occasionally rounded to // SF/DFmode (when storing into memory from the 387 stack). Maybe -// this is ok as well though it is just occassionally more precise. ?? +// this is ok as well though it is just occasionally more precise. ?? static void frange_arithmetic (enum tree_code code, tree type, @@ -2036,7 +2036,7 @@ foperator_unordered_equal::op1_range (frange &r, tree type, r = op2; // Add both zeros if there's the possibility of zero equality. frange_add_zeros (r, type); - // Add the posibility of a NAN. + // Add the possibility of a NAN. r.update_nan (); break; @@ -2047,7 +2047,7 @@ foperator_unordered_equal::op1_range (frange &r, tree type, r.set_undefined (); else { - // The false side indictates !NAN and not equal. We can at least + // The false side indicates !NAN and not equal. We can at least // represent !NAN. r.set_varying (type); r.clear_nan (); @@ -2674,7 +2674,7 @@ private: // result +0.0. So, all we can say for that case is if the // signs of divisor and dividend are always the same we have // [+0.0, +INF], if they are always different we have - // [-INF, -0.0]. If they vary, VARING. + // [-INF, -0.0]. If they vary, VARYING. // If both may be +-INF, divisor could be INF and dividend FLT_MAX, // in which case result is going to INF or vice versa and // result +0.0. So, all we can say for that case is if the -- cgit v1.1