mirror of
https://github.com/gcc-mirror/gcc.git
synced 2026-05-06 14:59:39 +02:00
423eb6def7
value_range::set_type doesn't set the m_type of the underlying vrange; it merely sets m_vrange to use an appropriate vrange subclass for the given type. This confused me. This patch renames it to avoid other people being similarly confused. No functional change intended. gcc/ * data-streamer-in.cc (streamer_read_value_range): Update for renaming of value_range::set_type to value_range::set_range_class. * gimple-range-gori.cc (gori_compute::compute_operand_range): Likewise. (gori_compute::compute_operand1_and_operand2_range): Likewise. (gori_stmt_info::gori_stmt_info): Likewise. (gori_calc_operands): Likewise. (gori_name_helper): Likewise. * ipa-cp.cc (ipcp_vr_lattice::set_to_bottom): Likewise. * ipa-cp.h (ipcp_vr_lattice::init): Likewise. * ipa-fnsummary.cc (evaluate_properties_for_edge): Likewise. * ipa-prop.cc (ipa_vr::get_vrange): Likewise. * range-op.h (range_cast): Likewise. * value-range.h (value_range::set_type): Rename to... (value_range::set_range_class): ...this, and add a note to the leading comment that it doesn't set the type of the underlying vrange. (value_range::init): Add a similar note to the leading comment. gcc/analyzer/ * svalue.cc (binop_svalue::maybe_get_value_range): Update for renaming of value_range::set_type to value_range::set_range_class. (unaryop_svalue::maybe_get_value_range): Likewise.
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.